Re: incubator_senssoft Repo

["Gimenez, Clayton C." <cg...@draper.com>]

Hi Lewis,

As we push towards the 1.0 release, we¹re also building the website, and
we¹ll need a repo to keep it in.  A while back, I submitted a request to
Infra, and they responded that you would need to use
https://reporeq.apache.org/ for us.  I¹ve tried, but don¹t appear to have
required permissions.  Can you request the repo for us?

As far as names go, I favor a general ³incubator-senssoft² repo, for
development of project-level concerns like the website and system
deployments (like combined Docker images of Distill/Userale/Tap).

Thanks and Happy Holidays!
Clay




On 11/22/16, 6:09 PM, "Poore, Joshua C." <jp...@draper.com> wrote:

>Hi Lewis,
>
>We'll look after the release as per www.apache.org/dev/#releases, your
>guidance in the process will be MUCH appreciated.
>
>As per the roadmap on the JIRA board:
>
>What you're seeing is a roadmap that extends beyond SensSoftv1.0.0
>
>SensSoft v1.0.0 includes:
>
>UserALE.js v .2
>Distill v 0.1.3
>TAP v 0.0.1
>
>(and all supporting APIs, etc., within a nice container)
>
>UserALE.PyQt5 and STOUT are non-essential extensions for logging for
>web-app usability, and aren't at this point meant to be included in the
>first release (PyQt5 is for desktop apps written in python, when we
>develop a version of UserALE for another language (e.g., C#) we might
>bundle up a desktop SensSoft release).
>
>UserALE.js v.3,.4 and Distill 0.1.4 will be added to SensSoft v1.1.0.
>
>Does that make sense?
>
>Josh
>
>
>Joshua C. Poore, Ph.D.
>Senior Member of the Technical Staff
>Draper
>555 Technology Square, Rm. 2242
>Cambridge, MA 02139-3563
>Phone: (617) 258-4023
>Cell: (617) 352-1700
>Email[1]: jpoore@draper.com
>Email[2]: poorejc@apache.org
>Participate in Operation XDATA: http://xdataonline.com!
>
>
>
>
>
>-----Original Message-----
>From: lewis john mcgibbney [mailto:lewismc@apache.org]
>Sent: Monday, November 21, 2016 12:49 PM
>To: dev@senssoft.incubator.apache.org
>Subject: Re: incubator_senssoft Repo
>
>Hi Josh,
>
>On Mon, Nov 21, 2016 at 7:22 AM, <
>dev-digest-help@senssoft.incubator.apache.org> wrote:
>
>> From: "Poore, Joshua C." <jp...@draper.com>
>> To: "dev@senssoft.incubator.apache.org"
>> <dev@senssoft.incubator.apache.org
>> >
>> Cc:
>> Date: Mon, 21 Nov 2016 15:21:07 +0000
>> Subject: RE: incubator_senssoft Repo
>> @Lewis,
>>
>> No, this is for a repo to collect our full releases (e.g., packages of
>> applications published in deployable formats). The website will need
>> its own repo.
>>
>>
>OK. We'll there are a few hurdles first.
>Initially, I've created our dev and release staging areas as follows
>
>https://dist.apache.org/repos/dist/dev/incubator/senssoft
>https://dist.apache.org/repos/dist/release/incubator/senssoft
>
>The dev one is used to stage whilst we conduct a VOTE internally within
>the Senssoft community and then over n general@incubator. The release
>area is for use when the VOTE passes and we are ready to ship the release.
>
>Until then, there is a procedure to be followed (this is mandatory for
>all Incubator projects wishing to release incubating artifacts as
>official releases). The documentation can be seen at
>http://www.apache.org/dev/#releases
>
>I am fine with undertaking the initial release management procedure and
>documenting it thoroughly over on our wiki. If this is fine with folks
>then I will progress whenever you give the green light.
>
>First things first, lets get the Roadmap sorted out.
>https://issues.apache.org/jira/browse/SENSSOFT/?selectedTab=com.atlassian.
>jira.jira-projects-plugin:roadmap-panel
>Right now it seems that there are a number of issues open for several
>components. Is it your intention to bump everything to 1.0.0 version?
>
>Lewis
>________________________________
> Notice: This email and any attachments may contain proprietary (Draper
>non-public) and/or export-controlled information of Draper. If you are
>not the intended recipient of this email, please immediately notify the
>sender by replying to this email and immediately destroy all copies of
>this email.
>________________________________

________________________________
 Notice: This email and any attachments may contain proprietary (Draper non-public) and/or export-controlled information of Draper. If you are not the intended recipient of this email, please immediately notify the sender by replying to this email and immediately destroy all copies of this email.
________________________________