One of the capabilities the new funded development policy gives us is
the ability to specify some projects as immediately fundable, without
needing to wait the proscribed 6 months.
I would like to propose we select a few projects to pre-approve, in
order to prime the pump, and to serve for testing out the process.
When we started this whole effort, KK suggested a number of good
projects. These perhaps need a bit more elaboration but give
something to select from.
Would you guys please look through this list for 2-3 projects you think
would make good initial fundable projects? Nominate ones that are
well-contained and straightforward - things that would make appropriate
GSoC projects for example. Please feel free to expound on the project
I'll collect everyone's nominations into a list, and we'll vote on
them. Projects that get >50% vote will be made pre-approved.
0: See "Section 6: Process Exceptions"
I'd like to get the developer book campaign done before the holiday
season this year.
The proposal is in board-docs:
Differences with last year are:
- *sum* of ohloh.net 12-month rankings for Inkscape *and lib2geom*
- extended book choice: Stackoverflow list of good C++ books
We had a bit of a discussion on IRC about this. For simplicity, I think
it'd be good if we keep this a developer education campaign, i.e. C++
books. And then have another something for the non-coders. We of course
appreciate those efforts too, I just don't know how to "rank" them and
what to give.
Something fun was proposed: add randomization to it. So, we pick 10 out
of the top 25 committers. The picking is done randomly, where your
win-chance is proportional to your commit count (p = your #commits /
The Jenkins server seems to work well. Today we got extra space (30GB
total now), so now we should have plenty for:
- trunk build, unittest, etc.
- release, unittest, etc.
- rendertest (trunk only?)
- 2geom trunk, tests, etc.
1. I want to give more people access to Jenkins. If only to be able to
restart builds if something simple goes wrong (bzr sometimes crashes,
which fails the build. Simply clicking the Build Now button fixes that).
Ping me on IRC for login details. I prevented people from signing up,
because it quickly creates a mess of users in my previous experience.
Perhaps there is a better way.
Access rights are pretty granular btw. No root rights required for
everybody, keeping OSUOSL happy.
2. I would greatly appreciate it if someone can help me to quickly
forward port 80 to 8080, so that we can access jenkins simpler through
3. Bryce, when we have released and things are quieter for you, let's
set up Coverity together.
4. Simple mail send-only capability must be set up. I have no
experience with this. Help is welcome.
5. I'll try to get rendertests going. Tomasz's branch output looks great.
6. Remember Josh's post about inkscape-tester, sign up for it!
Our next IRC board meeting is schedule for Wednesday, November 12th,
20:00 UTC. The agenda and IRC channel info can be found at:
Everybody is welcome to join the discussion. This is an important
meeting as we need to finalize some of the details for the LGM Hackfest.
We need to decide:
* Place (Toronto or Boston)
* Date (before or after LGM)
* Duration (two or three days)
You can read more about the proposed meet up at:
See you Wednesday,
(just got back from a very nice long weekend at the GSoC summit in
San Jose :))
We had a nice discussion with Brad and Karen over lunch at the GSoC
summit. What came up is having regular board meetings. I think this
would be great for us and make things a bit more structured / easier to
follow. How about we schedule a meeting (for board only) once every
month, e.g. every first Monday of the month?
What do you think?
To help move the code of conduct forwards, we've (by which I mean Maren)
has put together a draft page. All board members have editing rights on
the website so you should be able to edit it directly if you need to.
Once you're happy with the draft, we'll make it live (in the menu) and
add links from various social spots such as the comment boxes and IRC
page. So do respond to this email with your thoughts too.
Thanks for your time.
Best Regards, Martin Owens