The LGM hackfest is a possibility if we request it. They were just letting us know that it's an option.
On Sun, Dec 1, 2013 at 4:33 PM, Susan Spencer <susan.spencer@...400...>wrote:
I have not been able to find email addressses for Michael Wybrow, Peter Moulder, Kryztov Kosinski, and Sebastian Goette
If anyone has this info can you please forward to me, or contact them yourself and have them contact me.
This would be greatly appreciated. Thanks!
On Sat, Nov 30, 2013 at 11:03 PM, Susan Spencer <susan.spencer@...400...>wrote:
So the most likely team to identify remaining work for connector & layout tools is:
Michael Wybrow Peter Moulder Krystof Kosinski Sebastian Goette
On Sat, Nov 30, 2013 at 6:44 PM, Jabiertxo Arraiza Cenoz < jabier.arraiza@...2893...> wrote:
I could help in testing, design and some develop.
El sáb, 30-11-2013 a las 14:22 -0600, Susan Spencer escribió:
The participant leads from this thread are:
- Dick Bulterman (head of Distributed and Interactive Systems at
Centrum Wiskunde & Informatica (CWI) , 2. Martin Owens (dev & fund raising
- Rei Kagatsuki (dev & fund raising)
- HadiM (fund raising)
Any other suggestions or volunteers?
On Sat, Nov 30, 2013 at 1:47 PM, Martin Owens <doctormo@...400...> wrote: Hey Susan,
This is a great list. I'd like to put myself forward for both design and programming. Publishing updates and making videos showing progress also available. We should secure some space/resource for testers too. All the best, Martin Owens On Sat, 2013-11-30 at 13:39 -0600, Susan Spencer wrote: > As mentioned previously in this thread, > details of fundraising are typically > > discussed *after* a proper estimate is > developed. > > > If this is a serious discussion (which I believe it is) > then the following actions are up next: > > > 1. Identify the programmers, testers, documenters and users > who will participate. (Participants can assume multiple roles) > > > 2. The programmers collaborate to create & share the > requirements and constraints > > > 3. The testers specify & share the testing and signoff > requirements, based on output of #2 > > > 4. All participants specify documentation requirements to meet > needs of both the users and the future developers/maintainers > > > 5. Estimate the cost & delivery schedule > > > 6. Design the fundraising campaign (which is another separate effort) > > > > > if you're going to raise funds from the public then > you can't be code cowboys about this, no matter > if you believe this is a relatively small effort. > > > Performing the above steps and publishing the results > helps build momentum for public monetary support > and creates tremendous public confidence. > > > it also gives the tech media something to report > regularly building up to the fundraising > start date. Use the machine wisely, publicity never hurts! > > > Assuming that remote collaboration results require > more time than face-to-face sprints, > we can shoot for 30 to 60 days for #1-5, > 30 days maximum for #6, > > so max 90 days till fundraising. > > > My skills aren't in programming, > but if you would like me to I can help with > project development & fundraising. > If there are others more connected to Inkscape than I > who would like to step up for this work, please do! > > > > > - Susan > > > > > > > > > >
Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into
your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of
AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clk...
_______________________________________________ Inkscape-devel mailing
list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel