Thank you for your input! I was intended to link it to bug 47742 but my
but report was marked duplicate to 43133 and closed after the previous
email was send out. Although I don't agree with that decision but I'm
not sure if I should reopen my report. So right now it links to bug 43133.
I will rethink the time allotment and update on the proposal. Thank you!
(Sorry for the confusion that I directly replied to Sumana)
On 4/26/2013 1:59 PM, Sumana Harihareswara wrote:
On 04/26/2013 01:48 PM, Tongbo Sui wrote:
Here is my proposal for a VisualEditor plugin.
Thank you very much for your time.
Wikitech-l mailing list
Hi and welcome to our community, Tongbo Sui.
Did you mean to link to Bug 43133, "VisualEditor: Fly-out wikitext
editor for alienated content"?
You should scope your proposal at about 6 weeks of coding work and
dedicate the entire last month of the summer to bugfixing and code
review. In the past, proposals that allotted less than that for merging
with trunk, pre-deploy code review, testing and bugfixes, documentation,
and integration just didn't get to their goals at the end of the summer.
I think smaller scoping would have helped, so in the future, I think we
should simply not accept proposals that do not allot at least a third of
the summer to code review and response to code review. (And I think
you'll need more ramp-up time during the Community Bonding Period than
you have allotted here.)
Best of luck!