Re: permissions & owners on w.a.o/dist/incubator/uima
On Dec 25, 2007 3:23 AM, Marshall Schor <[EMAIL PROTECTED]> wrote: > When putting files into this spot, I think the permissions should > include group writable - so others in the project can update things, and > world read-only for obvious reasons. +1 > Is there a group for "uima"? I think there may not be, but I don't > remember how to check that on linux. or FreeBSD ;-) i use: grep incubator /etc/group but those with more BSD-fu usually have more elegant solutions than mine... > If there is not, then we should > make the group be "incubator" if possible. +1 the basic infrastructure rule is one group per TLP. so, whilst UIMA is in the incubator, the incubator group should be used. if UIMA gradulates to a TLP then a new uima group will be created and that group should be used for releases. if UIMA graduates as a subproject of Project Cool (say) then group cool will be used for releases. - robert
Re: permissions & owners on w.a.o/dist/incubator/uima
Thanks, Robert. I think we've finished with the tasks needed for migrating to the "mirror" system, perhaps with the exception of setting up .htaccess on w.a.o/dist/incubator/uima, and adding HEADER.html and README.html to that directory. However, I see other projects do not necessarily have that. Are any other lines (e.g., redirects of some sort) needed in the .htaccess file at this time? We would appreciate any "checking" you could do of our work to migrate to the mirror system. Thanks for all your help. -Marshall Robert Burrell Donkin wrote: > On Dec 25, 2007 3:23 AM, Marshall Schor <[EMAIL PROTECTED]> wrote: > >> When putting files into this spot, I think the permissions should >> include group writable - so others in the project can update things, and >> world read-only for obvious reasons. >> > > +1 > > >> Is there a group for "uima"? I think there may not be, but I don't >> remember how to check that on linux. >> > > or FreeBSD ;-) > > i use: > > grep incubator /etc/group > > but those with more BSD-fu usually have more elegant solutions than mine... > > >> If there is not, then we should >> make the group be "incubator" if possible. >> > > +1 > > the basic infrastructure rule is one group per TLP. so, whilst UIMA is > in the incubator, the incubator group should be used. if UIMA > gradulates to a TLP then a new uima group will be created and that > group should be used for releases. if UIMA graduates as a subproject > of Project Cool (say) then group cool will be used for releases. > > - robert > > >
Re: permissions & owners on w.a.o/dist/incubator/uima
On Dec 29, 2007 3:56 PM, Marshall Schor <[EMAIL PROTECTED]> wrote: > Thanks, Robert. > > I think we've finished with the tasks needed for migrating to the > "mirror" system, perhaps with the exception of setting up .htaccess on > w.a.o/dist/incubator/uima, and adding HEADER.html and README.html to > that directory. However, I see other projects do not necessarily have > that. policy is really pretty simple. the incubator insists that artifacts go under w.a.o/dist/incubator/uima. infrastructure insists that releases are mirrored, permissions are correct and that signatures+sums are uploaded for every artifact. the rest is up to the community to decide. most projects have a lot more ceremony, rules and traditions. these often evolve over time and it is common for projects to release too late that they need to be documented. podlings should be able to short circuit this process by taking a look at the documented best practices and picking out the ones they like. these can form the basis of a release management document for the podling. it's easier to modify and add new practices than to start from nothing. HEADER.html and README.html give a professional look but are not policy. if UIMA thinks they are worth the effort then add them to UIMA's release documentation, if not then that's fine. - robert
Re: permissions & owners on w.a.o/dist/incubator/uima
On Dec 29, 2007 3:56 PM, Marshall Schor <[EMAIL PROTECTED]> wrote: > Thanks, Robert. > > I think we've finished with the tasks needed for migrating to the > "mirror" system, perhaps with the exception of setting up .htaccess on > w.a.o/dist/incubator/uima, and adding HEADER.html and README.html to > that directory. However, I see other projects do not necessarily have > that. > > Are any other lines (e.g., redirects of some sort) needed in the > .htaccess file at this time? i've added the redirects to the appropriate .htaccess file over in people.apache.org. if you try http://people.apache.org/dist/incubator/uima, it should redirect to the archives. when your retire a release from the main download site to the archives, you may want to add redirects to the archives. however, since these URLs should not be used directly (they bypass the mirrors), it's reasonable just to change the links from your download documents. > We would appreciate any "checking" you could do of our work to migrate > to the mirror system. looks fine to me (not sure if you're bothered but) when using mirrors, the download stats collected from binary hits will no longer accurate. some projects use google analytics to collect this information. > Thanks for all your help. and thanks for acting as guinea pigs :-) i need to write this up so if anyone has any spare cycles to help improve the documentation or provide examples, that'd be much appreciated - robert
