forwarded to udig-developer list to discuss about the next steps..
WIth the 1.4.0 tag in place we are likely to vanish from the face of the > internet as we switch repositories, only to emerge renewed after an IP > check. not sure weather its a good idea to re-release with the same Version number after IP check is done. IMHO we need a clear cut - for users and developers - to emphasize something has changed. In addition I assume we have to change the code basis during IP check -process (changed dependencies, changing headers again, etc.) that the current release is based on something else (we don't know at the moment) and therefor I would prefer to re-release with a different version number. Whether we should increase the minor or major version it's not that important. I would be fine with a 1.5/1.4.1 or even 2.0. To start going through the IP we are taking the current release tag 1.4.0. Seem that we do not transfer the whole history as a git repository, which is fine as long as we have the chance to set the current repo at github read-only. With this in mind, I've the following questions: - How do we handle changes on master once the IP process has been started? (e.g. set it read-only and announce this on udig-developer mailing list) - What about the community repository, do we migrate it as well or leave it where it is? - Which docs from the udig-docs repository are in question to move to LocationTech as well? (user/devel as well as the walkthrough's (except uDigWalkthrough3.odt) we already migrated to udig-platform/docs. Afterwards we can set this repository to read-only as well, can't we? - How do we organize in the future? - Do we still use JIRA/Confluence or do we move to Eclipse-Bugzilla ( https://bugs.eclipse.org/bugs/describecomponents.cgi)? - Any plans to create a project "udigGIS"/"udig" in Bugzilla? - Does provide http://locationtech.org any infrastructure for this? Many questions I know, lets start with the IP! @Jody : do we already provided a ZIP of the 1.4.0 TAG? If not, who is responsible for? Opinions? Does have the Eclipse Foundation any other suggestions or requirements? Cheers Frank 2013/3/25 Jody Garnett <jody.garn...@gmail.com> > If it helps Frank, those eclipse pages indicate they are willing to phone > your employer and answer questions. > > WIth the 1.4.0 tag in place we are likely to vanish from the face of the > internet as we switch repositories, only to emerge renewed after an IP > check. > > -- > Jody Garnett > > On Friday, 15 March 2013 at 8:33 PM, Frank Gasdorf wrote: > > Benjamin, Jody, > thanks for your support. I've already filled out everything and just > waiting to get "Eclipse Committer Employer Consent Form" signed from my > managing Director. Hope to get the signature till end of next week. After > that I'll send a fax to Eclipse foundation. > Thanks again, > Frank > > > 2013/3/15 Benjamin Cabé <bc...@sierrawireless.com> > > Hello Frank, > > Using you Eclipse Bugzilla credentials, you should login to > http://portal.eclipse.org/ . From there, you should be able to fill-in > the committer questionnaire. > > Let me know if you need further assistance! > Benjamin-- > > De : Jody Garnett <jody.garn...@gmail.com> > Date : vendredi 15 mars 2013 00:00 > À : Frank Gasdorf <frank.gasd...@gmail.com> > Cc : Benjamin CABE <bc...@sierrawireless.com> > Objet : LocationTech Access > > I know you sorted out what was needed yesterday, Wayne was kind enough to > check up on where the team is with respect to getting access. > > Your name came back with the following: > Frank Gasdorf – Individual Committer Agreement, Employer Consent > > Our mentor Benjamin should be able to answer any questions you have. I > followed the instructions > here<http://wiki.eclipse.org/Development_Resources/HOWTO/Nominating_and_Electing_a_New_Committer#What_paperwork_do_I_need_to_fill_out.3F> > . > > Jody Garnett > > > >
_______________________________________________ User-friendly Desktop Internet GIS (uDig) http://udig.refractions.net http://lists.refractions.net/mailman/listinfo/udig-devel
