I'd like to offer any funds that were to be allocated for my attendance to be re-allocated to a developer or other member of the community who has shown interest in the project. I think it's a great idea to be more inclusive with reimbursement in terms of contributions rather than commits. Also, I'm ordering some metallic inkscape stickers on a roll this weekend for general purpose distribution and outreach activities. Looking at a few thousand, so there should be plenty. Maybe they could be handed out at LGM and the Hackfests. There was an idea for a community day - a special day where we invite people to come speak with Inkscape developers. This takes place during the hackfest, and since it's only one dedicated day it will not have a negative effect on development work during the hackfest. It would be cool to have a presentation for people to see. Maybe someone could show some tips and tricks for getting things done faster in Inkscape, and an "ask a developer" portion where people can just ask questions. It would help to attract people into positions we need filled if we have a list of them. Maybe we can offer special contributor stickers to people who pick up the shovel. Maybe based on our "hats" graphics from the website.
Just some ideas. Yea, it's a little late this year, but next year we could have a lot done. I'll still have stickers for you this year. :) -C On Fri, Jan 19, 2018 at 8:56 PM, Bryce Harrington <[email protected]> wrote: > When drafting the vote for this coming hackfest, a couple things > occurred to me regarding making our events more welcoming and inviting. > > First, while I like the fairness of our reimbursement schedule for > longer term contributors, I wonder if it might be a bit exclusionary for > situations where we do want to encourage newer developers to get > involved and join in. It makes me wonder if we should revisit the tiers > and make sure the numbers aren't hindering attendance at these events? > > Second, the tiers quantify based on patchcount, but many of our > developers are making numerous important contributions that can't be > measured in git commits. Where we do use a tiered system, it would be > beneficial if we could find ways to structure it to recognize that > work. > > Lastly, I worry a bit that not all types of people may feel comfortable > attending a hackfest - language, gender, age, work duties, family > requirements, etc. can affect someone's choice to attend. We invest a > fair amount of the project's money into these hackfests, but if they are > only effectively open to a subset of our membership it makes me wonder > if we need to broaden our thinking for other kinds of gathering > activities that might suit some of these other participants. > > Anyway, nothing here to do regarding the upcoming hackfest, time's too > short. But what do you guys think of these ponderings in relation to > making our future activities more inclusive of a wider variety of > people? > > Bryce > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Inkscape-board mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/inkscape-board ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Inkscape-board mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/inkscape-board
