On Wed, Dec 15, 2010 at 8:23 AM, Michael Renzmann <mrenzm...@otaku42.de> wrote: > >> There are people who would be happy to help, but they need an exact >> list of things that should be done. It can be kept it in t-h.o wiki. > > I'll try to compose such a list as soon as possible.
Just let us know when we can ping you. =) >>> The volunteer(s) will get full SSH access to the (virtual) server that >>> trac-hacks.org is running on as well as to the PostgreSQL database used >>> for the site. >> Snapshot of repository and DB (without accounts credentials) will be >> more useful. > > I'm not sure I understand the reasons you think this approach would be > more useful. Could you please explain it? 1. Several people can work simultaneously 2. People without SSH access will be able to help 3. You can run data migrations several times before deploying to production 4. You may experiment with features more freely (when developing, I usually have several Trac instances running) 5. You can work in familiar environment installed on your machine (IDE, tools etc.) 6. One-click download of test environment will greatly help people with patching any trac-hack plugin. I think that many plugins are not given an appropriate patches just because setting up development environment is not trivial. Plugins that need to be upgraded for t-h.o transition are no different. -- anatoly t. _______________________________________________ th-users mailing list th-users@lists.trac-hacks.org https://lists.trac-hacks.org/mailman/listinfo/th-users
