Board Meeting @ Friday May 6th, 2016
May's meeting is coming up. It'll be in #inkscape-devel at noon Pacific time (2000 UTC).
http://wiki.inkscape.org/wiki/index.php/Board_Meetings
This will be a good opportunity to debrief from the hackfest and identify followup actions that the board should work on in coming months.
Bryce
On Tue, 2016-05-03 at 12:34 -0700, Bryce Harrington wrote:
May's meeting is coming up. It'll be in #inkscape-devel at noon Pacific time (2000 UTC).
I believe that should be 1900 UTC due to summer time (21:00 CEST). See link at:
http://wiki.inkscape.org/wiki/index.php/Board_Meetings This will be a good opportunity to debrief from the hackfest and identify followup actions that the board should work on in coming months.
On Wed, May 04, 2016 at 02:34:30PM +0200, Tavmjong Bah wrote:
On Tue, 2016-05-03 at 12:34 -0700, Bryce Harrington wrote:
May's meeting is coming up. It'll be in #inkscape-devel at noon Pacific time (2000 UTC).
I believe that should be 1900 UTC due to summer time (21:00 CEST). See link at:
Thanks, damn daylight savings always screws me up.
Bryce
http://wiki.inkscape.org/wiki/index.php/Board_Meetings This will be a good opportunity to debrief from the hackfest and identify followup actions that the board should work on in coming months.
On Tue, 2016-05-03 at 12:34 -0700, Bryce Harrington wrote:
This will be a good opportunity to debrief from the hackfest and identify followup actions that the board should work on in coming months.
I'm almost done with collecting receipts from the hackfest and LGM. We spent roughly $7200 (plus or minus a few hundred dollars) out of the $13100 budgeted.
This hackfest was very successful in my opinion. Part of the reason it was so successful was having (somewhat accidentally) critical masses to work on the CMake build as well as GTK3 problems. I think we could duplicate this success by having some focused hacking sessions. In particular, I think it would be quite beneficial to have a gathering focused on getting 0.92 out. A follow up gathering could focus in fixing GTK 3 issues. Both these topics should be exciting to our user community which would help with raising funds to cover their costs.
Tav
On Wed, 2016-05-04 at 15:02 +0200, Tavmjong Bah wrote:
On Tue, 2016-05-03 at 12:34 -0700, Bryce Harrington wrote:
This will be a good opportunity to debrief from the hackfest and identify followup actions that the board should work on in coming months.
I'm almost done with collecting receipts from the hackfest and LGM. We spent roughly $7200 (plus or minus a few hundred dollars) out of the $13100 budgeted.
This hackfest was very successful in my opinion. Part of the reason it was so successful was having (somewhat accidentally) critical masses to work on the CMake build as well as GTK3 problems. I think we could duplicate this success by having some focused hacking sessions. In particular, I think it would be quite beneficial to have a gathering focused on getting 0.92 out. A follow up gathering could focus in fixing GTK 3 issues. Both these topics should be exciting to our user community which would help with raising funds to cover their costs.
Is it worth trying to have a release made upon every hackfest? That way we'd:
a) Always have a focus b) prepare with bug cleaning weeks before c) Share knowledge about making a release for different platforms d) Having something big to shout about afterwards
Martin,
On Wed, May 04, 2016 at 03:02:24PM +0200, Tavmjong Bah wrote:
On Tue, 2016-05-03 at 12:34 -0700, Bryce Harrington wrote:
This will be a good opportunity to debrief from the hackfest and identify followup actions that the board should work on in coming months.
I'm almost done with collecting receipts from the hackfest and LGM. We spent roughly $7200 (plus or minus a few hundred dollars) out of the $13100 budgeted.
This hackfest was very successful in my opinion. Part of the reason it was so successful was having (somewhat accidentally) critical masses to work on the CMake build as well as GTK3 problems. I think we could duplicate this success by having some focused hacking sessions. In particular, I think it would be quite beneficial to have a gathering focused on getting 0.92 out. A follow up gathering could focus in fixing GTK 3 issues. Both these topics should be exciting to our user community which would help with raising funds to cover their costs.
Excellent ideas all around.
With releases traditionally the work falls into these categories:
0. Getting tests to all pass and the build to build cleanly 1. The actual release mechanics (make dist, signing, etc.) 2. Translation 3. Fixing release-critical bugs 4. PR/announcement 5. Website/infrastructure related bits and pieces
Some of these may be better suited to co-location than others. #0 I suspect is probably already in the bag, and #1 I've been working on behind the scenes so am not worried there. Translation I think kind of by definition is going to be hard to do as a hackfest. The PR and Website stuff probably would benefit from a hackfest but they're not areas likely to be blockers for us, although a strong case could be made from a fundraising perspective that it would be time well invested.
I suspect for this release bugfixing is the biggest remaining hurdle, but I don't have anywhere close to a handle on what it's going to look like so who knows. If we knew what bugs needed fixed the worst, and who the fixers would be, that would tell us the suitability of a hackfest and clue us in on where geographically it should be held.
I'm guessing that there's enough of us typically involved in releases that are located in the western half of the US, that a west-coast or midwest location might be sensible, and might be a fair turn since we've had hackfests on the east coast and England.
Bryce
On Wed, 2016-05-04 at 21:12 -0700, Bryce Harrington wrote:
On Wed, May 04, 2016 at 03:02:24PM +0200, Tavmjong Bah wrote:
On Tue, 2016-05-03 at 12:34 -0700, Bryce Harrington wrote:
This will be a good opportunity to debrief from the hackfest and identify followup actions that the board should work on in coming months.
I'm almost done with collecting receipts from the hackfest and LGM. We spent roughly $7200 (plus or minus a few hundred dollars) out of the $13100 budgeted.
This hackfest was very successful in my opinion. Part of the reason it was so successful was having (somewhat accidentally) critical masses to work on the CMake build as well as GTK3 problems. I think we could duplicate this success by having some focused hacking sessions. In particular, I think it would be quite beneficial to have a gathering focused on getting 0.92 out. A follow up gathering could focus in fixing GTK 3 issues. Both these topics should be exciting to our user community which would help with raising funds to cover their costs.
Excellent ideas all around.
With releases traditionally the work falls into these categories:
0. Getting tests to all pass and the build to build cleanly 1. The actual release mechanics (make dist, signing, etc.) 2. Translation 3. Fixing release-critical bugs 4. PR/announcement 5. Website/infrastructure related bits and pieces
Some of these may be better suited to co-location than others. #0 I suspect is probably already in the bag, and #1 I've been working on behind the scenes so am not worried there. Translation I think kind of by definition is going to be hard to do as a hackfest. The PR and Website stuff probably would benefit from a hackfest but they're not areas likely to be blockers for us, although a strong case could be made from a fundraising perspective that it would be time well invested.
I suspect for this release bugfixing is the biggest remaining hurdle, but I don't have anywhere close to a handle on what it's going to look like so who knows. If we knew what bugs needed fixed the worst, and who the fixers would be, that would tell us the suitability of a hackfest and clue us in on where geographically it should be held.
Yes, I was thinking work category 3 as the primary reason to have a release hackfest. Work on the other categories might also benefit from a hackfest but not as much as 3.
I'm guessing that there's enough of us typically involved in releases that are located in the western half of the US, that a west-coast or midwest location might be sensible, and might be a fair turn since we've had hackfests on the east coast and England.
It's a bit far away, but we will be able to send two people to the Google Mentor Summit which is in the later part of October. So timing a hackfest on the west coast at that time might be good. If not for a release then perhaps for working on GTK3.
Tav
Bryce
Just going to throw out that I can probably make some arrangements for a SCALE related hackfest (1st Q every year) and possibly get some sponsorship from the conference for speaking and/or volunteer work. There would just need to be enough spoken interest in advance for me to run it by the chairs. If we could really get a regular release process down directly linked to the conference I am pretty confident it would be an easy sell.
Cheers, Josh
On Thu, May 5, 2016 at 11:52 AM, Tavmjong Bah <tavmjong@...47...> wrote:
On Wed, 2016-05-04 at 21:12 -0700, Bryce Harrington wrote:
On Wed, May 04, 2016 at 03:02:24PM +0200, Tavmjong Bah wrote:
On Tue, 2016-05-03 at 12:34 -0700, Bryce Harrington wrote:
This will be a good opportunity to debrief from the hackfest and identify followup actions that the board should work on in coming months.
I'm almost done with collecting receipts from the hackfest and LGM. We spent roughly $7200 (plus or minus a few hundred dollars) out of the $13100 budgeted.
This hackfest was very successful in my opinion. Part of the reason it was so successful was having (somewhat accidentally) critical masses to work on the CMake build as well as GTK3 problems. I think we could duplicate this success by having some focused hacking sessions. In particular, I think it would be quite beneficial to have a gathering focused on getting 0.92 out. A follow up gathering could focus in fixing GTK 3 issues. Both these topics should be exciting to our user community which would help with raising funds to cover their costs.
Excellent ideas all around.
With releases traditionally the work falls into these categories:
- Getting tests to all pass and the build to build cleanly
- The actual release mechanics (make dist, signing, etc.)
- Translation
- Fixing release-critical bugs
- PR/announcement
- Website/infrastructure related bits and pieces
Some of these may be better suited to co-location than others. #0 I suspect is probably already in the bag, and #1 I've been working on behind the scenes so am not worried there. Translation I think kind of by definition is going to be hard to do as a hackfest. The PR and Website stuff probably would benefit from a hackfest but they're not areas likely to be blockers for us, although a strong case could be made from a fundraising perspective that it would be time well invested.
I suspect for this release bugfixing is the biggest remaining hurdle, but I don't have anywhere close to a handle on what it's going to look like so who knows. If we knew what bugs needed fixed the worst, and who the fixers would be, that would tell us the suitability of a hackfest and clue us in on where geographically it should be held.
Yes, I was thinking work category 3 as the primary reason to have a release hackfest. Work on the other categories might also benefit from a hackfest but not as much as 3.
I'm guessing that there's enough of us typically involved in releases that are located in the western half of the US, that a west-coast or midwest location might be sensible, and might be a fair turn since we've had hackfests on the east coast and England.
It's a bit far away, but we will be able to send two people to the Google Mentor Summit which is in the later part of October. So timing a hackfest on the west coast at that time might be good. If not for a release then perhaps for working on GTK3.
Tav
Bryce
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-board mailing list Inkscape-board@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-board
Just going to throw out that I can probably make some arrangements for a
SCALE related hackfest (1st Q every year) and possibly get some sponsorship from the conference for speaking and/or volunteer work. There would just need to be enough spoken interest in advance for me to run it by the chairs. If we could really get a regular release process down directly linked to the conference I am pretty confident it would be an easy sell.
I'm game. :) -C
Cheers, Josh
On Thu, May 5, 2016 at 11:52 AM, Tavmjong Bah <tavmjong@...47...> wrote:
On Wed, 2016-05-04 at 21:12 -0700, Bryce Harrington wrote:
On Wed, May 04, 2016 at 03:02:24PM +0200, Tavmjong Bah wrote:
On Tue, 2016-05-03 at 12:34 -0700, Bryce Harrington wrote:
This will be a good opportunity to debrief from the hackfest and identify followup actions that the board should work on in coming months.
I'm almost done with collecting receipts from the hackfest and LGM. We spent roughly $7200 (plus or minus a few hundred dollars) out of the $13100 budgeted.
This hackfest was very successful in my opinion. Part of the reason it was so successful was having (somewhat accidentally) critical masses to work on the CMake build as well as GTK3 problems. I think we could duplicate this success by having some focused hacking sessions. In particular, I think it would be quite beneficial to have a gathering focused on getting 0.92 out. A follow up gathering could focus in fixing GTK 3 issues. Both these topics should be exciting to our user community which would help with raising funds to cover their costs.
Excellent ideas all around.
With releases traditionally the work falls into these categories:
- Getting tests to all pass and the build to build cleanly
- The actual release mechanics (make dist, signing, etc.)
- Translation
- Fixing release-critical bugs
- PR/announcement
- Website/infrastructure related bits and pieces
Some of these may be better suited to co-location than others. #0 I suspect is probably already in the bag, and #1 I've been working on behind the scenes so am not worried there. Translation I think kind of by definition is going to be hard to do as a hackfest. The PR and Website stuff probably would benefit from a hackfest but they're not areas likely to be blockers for us, although a strong case could be made from a fundraising perspective that it would be time well invested.
I suspect for this release bugfixing is the biggest remaining hurdle, but I don't have anywhere close to a handle on what it's going to look like so who knows. If we knew what bugs needed fixed the worst, and who the fixers would be, that would tell us the suitability of a hackfest and clue us in on where geographically it should be held.
Yes, I was thinking work category 3 as the primary reason to have a release hackfest. Work on the other categories might also benefit from a hackfest but not as much as 3.
I'm guessing that there's enough of us typically involved in releases that are located in the western half of the US, that a west-coast or midwest location might be sensible, and might be a fair turn since we've had hackfests on the east coast and England.
It's a bit far away, but we will be able to send two people to the Google Mentor Summit which is in the later part of October. So timing a hackfest on the west coast at that time might be good. If not for a release then perhaps for working on GTK3.
Tav
Bryce
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications
Manager
Applications Manager provides deep performance insights into multiple
tiers of
your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-board mailing list Inkscape-board@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-board
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications
Manager
Applications Manager provides deep performance insights into multiple
tiers of
your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Thu, 2016-05-05 at 23:20 -0700, Josh Andler wrote:
Just going to throw out that I can probably make some arrangements for a SCALE related hackfest (1st Q every year) and possibly get some sponsorship from the conference for speaking and/or volunteer work. There would just need to be enough spoken interest in advance for me to run it by the chairs. If we could really get a regular release process down directly linked to the conference I am pretty confident it would be an easy sell.
Sounds interesting. Might be a good alternative to holding a hackfest with LGM next year. (BTW, Josh, have you asked Felipe about Brazil yet?) The one disadvantage, is west coast US is a long way from Europe (as is Rio for that matter).
Tav
On Thu, 2016-05-05 at 23:20 -0700, Josh Andler wrote:
Just going to throw out that I can probably make some arrangements for a SCALE related hackfest (1st Q every year) and possibly get some sponsorship from the conference for speaking and/or volunteer work. There would just need to be enough spoken interest in advance for me to run it by the chairs. If we could really get a regular release process down directly linked to the conference I am pretty confident it would be an easy sell.
We're going to have a fight on our hands :-D
MIT SIPB are interested in helping us run our hackfest, several people in fact have gotten back to me with interest. The venue is free for the duration. It's in Boston, so nearer Europe and they run regular hackathons and hackfests with solid local interest.
The only issue is that the bigger events we can tie it to are perhaps not as exciting. LibrePlanet is a possibility for instance and was pretty big and well attended this year. But otherwise not much.
We'll probably have to weigh up the costs as well as the advantages to both venues.
Best Regards, Martin Owens
On Tue, May 03, 2016 at 12:34:18PM -0700, Bryce Harrington wrote:
May's meeting is coming up. It'll be in #inkscape-devel at noon Pacific time (2000 UTC).
http://wiki.inkscape.org/wiki/index.php/Board_MeetingsThis will be a good opportunity to debrief from the hackfest and identify followup actions that the board should work on in coming months.
Bryce
Thanks everyone for attending, that ended up being an impressively productive meeting. I've gone through the meeting log and pulled out action items:
http://wiki.inkscape.org/wiki/index.php/Board_Meetings
I've penciled in Friday, June 3rd as our next meeting, and jotted in an agenda to followup on a number of the items we touched on this week.
Bryce
participants (5)
-
Bryce Harrington -
C R -
Josh Andler -
Martin Owens -
Tavmjong Bah