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"
(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?
Maren Hachmann is adding commenting functionality into the website. We
have an empty link to a code of conduct page which we'd like to have,
which describes the kind of behavior expected of community
Untimely we want to be able to deal with flagged comments without
causing fuss. Having set rules and processes would be good.
If there is an existing CoC, we should copy it onto the website. Please
let me know either way.
Best regards, Martin Owens
I propose we have two hacking sessions:
The first would be at RedHat in January as proposed by Máirín Duffy.
This session would focus on GTK problems and the user-interface. I think
the opportunity to have RedHat GTK+ experts help us is too good of an
offer to pass up. A specific goal would be to improve the Mac OSX port
which is suffering from GTK related canvas redraw issues. I envision
this hacking session be small so it would be easy to organize. It would
be open to only those who have already dealt with GTK, Mac OSX,
interface issues, or have deep knowledge of the Inkscape code base.
Candidates to invite include: su_v, LiamW, Johan, JazzyNico, Alex
Valenis, and Jon Cruz. We can ask Martin to coordinate event. This can
be viewed as a "warm-up" session where we can gain some experience in
organizing this type of event.
The second hacking session would be at LGM in April. This would be a
larger session, open to all Inkscape developers and covering more
What do you all think?
Sorry if you're not the right person for this question. Please forward
tot he right person at the Conservancy.
I'm Martin, the webmaster for inkscape.org, we're currently offering the
ability to upload files into galleries (10MB quota) and soon will email
users alerts if they are involved with translations or when a new
release appears etc.
These website services should probably mean the website needs a terms
and conditions, which would inform users of the limits capacity and
service remit we're going for.
Something like: "this website and it's services are provided "as is",
and you should not expect the services to continue to work or serve any
particular need. Your files should never be assumed to be safe here and
you should back everything up. Plus we'll email you announcements and
other alerts if you want, see your profile settings for details."
We could do with some help putting together the right language in the
right way to make it clear to users.
Best Regards, Martin Owens