On 04/03/2013 11:11 AM, Ori Livneh wrote:
required. What you are proposing is considerably more ambitious in scope (Web Platform doesn't integrate with bug management and SCM), but some napkin cost analysis could be very useful.
Yes, but I didn't want to go too far with implementation details and budgeting before having some community feedback first (which we are getting now).
Then again, the proposal has enough level of detail to get a rough budget.
Before committing to the full scope of the project, it would be good to comb through this and identify one or two things that could be implemented easily and that would be expected to demonstrate a measurable impact on the number of new contributors. We should not wait for a project like this to be finished in toto before examining the correctness of the initial hypotheses.
Agreed.
http://www.mediawiki.org/wiki/Requests_for_comment/Wikitech_contributors#Fir... is supposed to be completed in 3 months, and even there you have some easier tasks that could be implemented pretty fast, namely forms & templates for
* User profiles. * Projects. * Tasks. * Events.
Notifications still require more definition and expertise to decide what should be done now. Is Echo ripe for this? Is it worth to use this experiment to prototype Flow there? Or should we fallback to a system like http://www.mediawiki.org/wiki/Extension:TranslationNotifications ...?
And then we have Nodes, which is a novel concept and probably requires more complex implementation work in therms of software development and design.
About design and usability... Yes, doing something amazing takes a long time (look at ourselves). Then again, this is parallel work. This project is not contesting Vector, neither the current look & feel. This proposal is first and foremost about the plumbing behind.
If you feel that more design resources / budget should be allocated on a nicer UI then I can also ask for it, but in a context of limited resources the priorities would be clear.