Opened 13 years ago
Closed 13 years ago
#802 closed task (fixed)
Trac/SVN/mailman for GeoMoose
Reported by: | EliL | Owned by: | warmerdam |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | SysAdmin | Keywords: | SAC, GeoMoose, Trac, Mailman |
Cc: | theduckylittle, jimk, elil, blammo, bfraser, bfischer, crschmidt, hobu, wildintellect |
Description
This is a request for OSGeo infrastructure for the GeoMoose Project. Specifically a request for Trac, SVN, and mailman infrastructure.
The GeoMoose project has continued to progress since application to Incubation (#147). Incubation is supposed to start moving along again too.
Currently we host our infrastructure on SF (http://sourceforge.net/projects/geomoose/) and various other private infrastructure.
Please make theduckylittle (Dan Little) administrator.
Change History (17)
comment:1 by , 13 years ago
comment:2 by , 13 years ago
Cc: | added |
---|---|
Keywords: | Mailman added |
Owner: | changed from | to
I am working on the lists transfer now.
Chris has agreed to work on the svn/trac next week. It has been suggested we do not need to transfer Trac content automatically.
We also need to go through the process of getting permission from SAC and the board. I'll take the action item on that.
comment:3 by , 13 years ago
We really don't need the Trac migrated. A fresh start is more than welcome.
comment:4 by , 13 years ago
Dan should be maillist admin and SVN admin. The initial list for svn commit access is theduckylittle, jimk, elil, blammo, bfraser, bfischer
comment:5 by , 13 years ago
OK, the mailing list has been migrated with the mailing list archive.
The list members should be notified of the new address, and perhaps the old list should be shut down. Also, be warned that all users are now regularly subscribed. So you might want to warn them if they were digest or something they need to change. Dan is setup as admin and can ask me by email if he does not know the (usual) mailing list admin password.
comment:6 by , 13 years ago
The email list does not seem to be archiving. http://lists.osgeo.org/pipermail/geomoose-users/ See also #667 if it is a similar cause.
comment:7 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
I'm sorry, it looks like I ran the archive import script as root instead of mailman. Could you try sending something to archive again and see if it is working now? I did:
chown mailman.mailman -R /var/lib/mailman/archives/private/geomoose-users
Reopen if it is still broken.
comment:8 by , 13 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Shoot, reopening since this ticket also addresses svn and trac.
comment:11 by , 13 years ago
Chris,
Is there anything the we or others need to do for this to proceed? Otherwise, do you have a timeline estimate?
Thanks, Eli
comment:12 by , 13 years ago
Cc: | added; removed |
---|---|
Owner: | changed from | to
Status: | reopened → new |
Folks,
Now that GeoMoose is officially in incubation I think we should move on this. I'll take the lead on the SVN and then trac steps.
follow-up: 15 comment:13 by , 13 years ago
Status: | new → assigned |
---|
I have grabbed a snapshot of your SVN dumped and loaded it up at OSGeo. Please review:
The following OSGeo userid have commit access and they can also add new users and remove users.
https://www2.osgeo.org/cgi-bin/auth/ldap_group.py?new_member=bfischer&group=geomoose&ou=svn
Let me know if we need to synchronize a re-migration from svn to avoid losing commits or there are any problems. Trac to follow...
comment:14 by , 13 years ago
SVN looks good as far as I can tell. It also appears complete (no missing commits). I'd like to hear from at least one more person to confirm.
That is the correct list of OSGeo userids.
comment:15 by , 13 years ago
Thanks, SVN and LDAP look good.
Also, Dan and I have completed reorganizing SVN to follow more standard naming conventions regarding branches/tags/trunk.
comment:17 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
http://trac.osgeo.org/geomoose now setup. The project owners have been setup with admin priveledges and should fix up the components, versions and related things via the Admin panel (left most edge of the top tab). Grab me in irc if you need assistance.
I think this concludes the requests in this ticket.
FYI: the SVN repository on SourceForge is available via: