On Mon, 7 Mar 2016 16:39:11 -0800 Bryan Richter <[email protected]> wrote:
> Doing so, of course, massively conflicts with the changes you (fr33) > are making; changes that are hard to make precisely because there's so > much dead weight. This causes me — and presumably you — some tension. Ah, I didn't know you were removing old code. Please don't let my patches interfere though. I worked hard (in the sense of lots of git grep and stack build, not intellectualy challenging or anything :P) to make all the chaos build after changing all the routes, but it can wait until you clean the code and re-do the /u/<name> changes on much smaller and simpler code. Actually, with such huge changes I expected conflicts. Here they are :P > > [ ... ] > > To be more *on* topic, the act of stripping out dead code is creating > some new tasks. I definitely want to share them and all that. > OpenProject is the tool to do it with. Can I pass the tasks on to > someone else who can take the time to figure out the best way to use > OpenProject? Personally I'm not exactly excited about taking that role, unless OP can be used conveniently from the terminal / text-based web browser / email client, but regardless - do we have a documented workflow for using it? Maybe you can push tasks to some TODO file / etherpad / email. So far I like the use of the dev ML and IRC for that: You mention a task, a dev picks it up and sends a patch or MR. The same applies to me and any other volunteer here: When someone has some idea / proposal / problem / suggestion, where do they put it? OP or mailing list or Snowdrift wiki? --fr33 _______________________________________________ Dev mailing list [email protected] https://lists.snowdrift.coop/mailman/listinfo/dev
