- Inkscape Devel - Inkscape Mailman

Next hackfest
by Krzysztof Kosiński 01 May '15

01 May '15

There were already some noises made at the hackfest about the next one, so I made a wiki page to record the very early planning / proposals: http://wiki.inkscape.org/wiki/index.php/Hackfest2016 The possible locations mentioned at this year's hackfest were London, Leeds and Warsaw. I added some information about London and Warsaw. I never visited Leeds, but Alex should be able to provide further information. Regards, Krzysztof

5 6

Re: [Inkscape-devel] [RFC] Plan for 0.92
by TimeWaster 30 Apr '15

30 Apr '15

sorry bryce, this was meant for the mailing list. i really dont get why the standard reply address isn't the mailing list... ok, i need a wiki account, thank you in advance... regards, TimeWaster On 28.4.2015 15:35, Bryce Harrington wrote: > Heya, ok just post a request on the mailing list and one of the admins > will take care of adding you asap. > > Bryce > > On Tue, Apr 28, 2015 at 11:15:30AM +0200, TimeWaster wrote: >> hi, >> >> i need a wiki account to add my stuff in the release notes. >> >> >> regards, >> TimeWaster >> >> >> On 28.4.2015 06:40, Bryce Harrington wrote: >> >Hi all, >> > >> >Last release we discussed switching to a more rapid release cycle >> >starting with 0.92. So here's a proposal for a plan to do this. >> > >> >Even though it's been a short time since our last release, already >> >we've >> >accumulated a number of features, thanks in large part to Jabier's many >> >LPE's: >> > >> > http://wiki.inkscape.org/wiki/index.php/Release_notes/0.92 >> > >> >Please make sure any other added features are included in the release >> >notes soon. >> > >> >I'd like to propose the following release plan, which is based on the >> >0.91 plan, but simplified and with more focus on changes to packaging, >> >no bug hunt, and no experimental branch. We simplify to a single >> >Freeze >> >phase. We cut a pre0 release before starting the build system hacking, >> >so testers will have something to test. We move the about screen >> >contest up so it can get done sooner, and so that we can string freeze >> >earlier to give translators time. This should drop a number of >> >the more >> >time consuming bits yet keep the important steps in the checklist. >> > >> >Please let me know what you think, and esp. if you see some areas that >> >need tweaking. >> > >> >Bryce >> > >> > >> ># Period Tasks >> >-------------------------- >> >1. Open development. >> > Post inkscape-0.92-pre0.tar.gz (w/ old build sys) >> > Start an About Screen contest >> > Decide new unit testing system >> > Decide new build system >> > Implement new build system >> > Integrate new swatch dialog >> > Begin switching packaging to use new build system >> > Begin tracking % translated >> > Migrate mailing lists off sourceforge >> > (Other bits off roadmap...) >> > >> >2. Chill. Development focuses on wrapping up >> > Disable features that aren't finished >> > Identify 'make distcheck' issues >> > Identify remaining writing needed for Release >> >Notes. >> > Identify any release blocker bugs >> > Recruit Release Wardens for Hard Freeze >> > >> >3. Frost. Only production-ready code committed to Mainline >> > Finalize any major changes to platform packaging >> > Inkscape must pass 'make distcheck' >> > Ensure packaging for all platforms installs >> > Ensure packaging for all platforms uninstalls >> > Finalize tutorials to be shipped with release >> > Finalize other docs included in the release >> > Finalize about screen >> > Finalize Release Notes except Known Issues >> > Post additional inkscape-0.92-pre*.tar.gz releases >> > Packagers test creating pkgs of the -pre* releases >> > Post % translated per language for each release >> > >> >4. Freeze. Stable Branch is forked from Mainline >> > Regular development resumes on Mainline. >> > Only Release Wardens can commit to Stable Branch >> > Cherrypick bug fixes from Mainline to Stable >> > Complete any late work under advisement of Wardens >> > Focus on release-critical bug fixing. >> > String Freeze No further string changes allowed on Stable >> >Branch. >> > Translators work on translations. >> > Finalize all extensions >> > Finalize codebase translations >> > Finalize Known Issues section of Release Notes >> > Finalize packaging scripts >> > Post additional inkscape-0.92-pre*.tar.gz releases >> > Post % translated per language for each release >> > >> >5. Release. Post inkscape-0.92.tar.gz >> > Post packages >> > Post official announcements >> > Plan 0.92.1+ release(s), if needed >> > >> >6. Open development. >> > >> > >> > >> >As far as timing goes, I'm thinking we give a few weeks to open >> >development (step 1), and then a week each for all the subsequent >> >steps. This would see 0.92 released in a June/July timeframe. >> > >> > >> >------------------------------------------------------------------------------ >> >One dashboard for servers and applications across >> >Physical-Virtual-Cloud >> >Widest out-of-the-box monitoring support with 50+ applications >> >Performance metrics, stats and reports that give you Actionable >> >Insights >> >Deep dive visibility with transaction tracing using APM Insight. >> >http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >> >_______________________________________________ >> >Inkscape-devel mailing list >> >Inkscape-devel(a)lists.sourceforge.net >> >https://lists.sourceforge.net/lists/listinfo/inkscape-devel

2 2

Accessibility Brainstorm for Hackfest // wiki access
by Amelia Bellamy-Royds 29 Apr '15

29 Apr '15

Hello all, I've arranged to hold a discussion with the Inkscape Hackfest team in Toronto this week about accessibility issues and SVG in general or Inkscape in particular. There are really two sides of accessibility when it comes to software like Inkscape: - making the software itself more accessible (e.g., can it be easier to navigate, or to change the UI styling to create high contrast or larger fonts/icons) - making it easier for Inkscape users to make accessible SVG (e.g., encouraging the inclusion of alt text, language attributes, ARIA attributes for interactive components, logical groupings/ordering of all objects and text) I was going to add some more notes to the agenda page for the Hackfest, but discovered the wiki is locked down against spammers. So, a quick request to those who hold the keys to the wiki to send me a log-in invite. For anyone else, if you have any thoughts on what is or isn't good or bad about accessibility issues and Inkscape, consider this a brainstorm email thread. I'll then try to compile the ideas from here and from the in-person discussion into a focused wiki page. Hopefully we can come up with a list of To-Dos, at least some of which might be classified as low-hanging fruit that can easily be picked. Best, Amelia Bellamy-Royds

3 3

[RFC] Inkscape Roadmap
by Bryce Harrington 29 Apr '15

29 Apr '15

Thanks Krzysztof, Martin, and Alex for providing feedback on the roadmap sketch I posted earlier. I've fleshed out the following roadmap draft using this feedback, and extended it for another 5 releases. This assumes roughly 3 months per release. http://wiki.inkscape.org/wiki/index.php/Roadmap If anything, I think I've squeezed too much; I'd been hoping to have no more than maybe 3 major items per release. If you see items that could be put off or that would be too difficult to achieve in the near term, let me know so we can bump them down the list. Particularly for 0.92 and 0.93. Even after squeezing all that stuff in, I've found quite a laundry list of feature requests left. If there are features that you think *must* go in pre-1.0, and you're planning on working on them yourself, please let me know and I'll shuffle things around to ensure it fits. Beyond that... any and all feedback is welcomed! Come throw some darts! Bryce

7 17

Beer search
by Jabier Arraiza 29 Apr '15

29 Apr '15

Hi any one could give me the direction of LGM fest for tonight?

2 1

decript(HF)
by Jabier Arraiza 29 Apr '15

29 Apr '15

To thouse dont have a glass ball to decript, the new branches are amelia and insaner.com

1 0

NIGHT 3
by Jabier Arraiza 29 Apr '15

29 Apr '15

Shhhhhhhhhhhh!!!

1 0

DAY 3
by Jabier Arraiza 29 Apr '15

29 Apr '15

Dedicated to Jenkins. A good day also. Our live is incremented by almost 100 years because new health to our group. Also a day to say goodbay, hope a see you later. Hackfest put a dot and continue. Thanks to all people who made this posibol, i think we have 73 points more in inkscape now. Bye

1 0

Improve docs for new devs
by Maren Hachmann 28 Apr '15

28 Apr '15

Hi devs, to make entering the project easy for new developers, we have a whole section of the website dedicated to development topics [1] We're looking for suggestions what to add / how to improve that section, especially the "Getting started" part [2]. It would be especially valuable if someone of the more recent new developers could make suggestions, as they've only just gone through the process themselves. I've added a link to the Doxygen pages, but there's probably more which could be useful to guide our future devs Any ideas are welcome! Regards, Maren [1] https://inkscape.org/en/develop/ [2] https://inkscape.org/en/develop/getting-started

1 0

[RFC] Plan for 0.92
by Bryce Harrington 28 Apr '15

28 Apr '15

Hi all, Last release we discussed switching to a more rapid release cycle starting with 0.92. So here's a proposal for a plan to do this. Even though it's been a short time since our last release, already we've accumulated a number of features, thanks in large part to Jabier's many LPE's: http://wiki.inkscape.org/wiki/index.php/Release_notes/0.92 Please make sure any other added features are included in the release notes soon. I'd like to propose the following release plan, which is based on the 0.91 plan, but simplified and with more focus on changes to packaging, no bug hunt, and no experimental branch. We simplify to a single Freeze phase. We cut a pre0 release before starting the build system hacking, so testers will have something to test. We move the about screen contest up so it can get done sooner, and so that we can string freeze earlier to give translators time. This should drop a number of the more time consuming bits yet keep the important steps in the checklist. Please let me know what you think, and esp. if you see some areas that need tweaking. Bryce # Period Tasks -------------------------- 1. Open development. Post inkscape-0.92-pre0.tar.gz (w/ old build sys) Start an About Screen contest Decide new unit testing system Decide new build system Implement new build system Integrate new swatch dialog Begin switching packaging to use new build system Begin tracking % translated Migrate mailing lists off sourceforge (Other bits off roadmap...) 2. Chill. Development focuses on wrapping up Disable features that aren't finished Identify 'make distcheck' issues Identify remaining writing needed for Release Notes. Identify any release blocker bugs Recruit Release Wardens for Hard Freeze 3. Frost. Only production-ready code committed to Mainline Finalize any major changes to platform packaging Inkscape must pass 'make distcheck' Ensure packaging for all platforms installs Ensure packaging for all platforms uninstalls Finalize tutorials to be shipped with release Finalize other docs included in the release Finalize about screen Finalize Release Notes except Known Issues Post additional inkscape-0.92-pre*.tar.gz releases Packagers test creating pkgs of the -pre* releases Post % translated per language for each release 4. Freeze. Stable Branch is forked from Mainline Regular development resumes on Mainline. Only Release Wardens can commit to Stable Branch Cherrypick bug fixes from Mainline to Stable Complete any late work under advisement of Wardens Focus on release-critical bug fixing. String Freeze No further string changes allowed on Stable Branch. Translators work on translations. Finalize all extensions Finalize codebase translations Finalize Known Issues section of Release Notes Finalize packaging scripts Post additional inkscape-0.92-pre*.tar.gz releases Post % translated per language for each release 5. Release. Post inkscape-0.92.tar.gz Post packages Post official announcements Plan 0.92.1+ release(s), if needed 6. Open development. As far as timing goes, I'm thinking we give a few weeks to open development (step 1), and then a week each for all the subsequent steps. This would see 0.92 released in a June/July timeframe.

3 2