[HacktionLab] Barncamp 2018

[mark]

Thanks for letting us know Ben.

One of the outputs of the survey was a whole bunch of information on who
is up for doing what. See pages 26-27 here:
https://hacktionlab.org/upload/7/73/BC2017survey_full.pdf

I would hope that the people who've committed to each task would be able
to form small working groups and crack on with it. I didn't put contact
details in that public doc, but hit me up if you need some. Now would be
a good time for that to start happening I guess? Maybe if anyone who's
only committed to one task was to kick off some correspondence with the
rest of the members of that task group, things would start happening? I
think that would help to decentralise the process.

Regarding technical solutions for organising, I'm not convinced that we
need to change from what we already have, but on the other hand if
people get energised by the need to set up and populate a new service,
fine, I'll join in when asked.

I think the important thing is that people start talking to each other
in small groups, make your group a wiki page, sketch up some plans, come
back to the mailing list if you've got something you think needs broader
input... you know the drill peeps...

I'm already excited about it :-)

Mark



Ben Green:
> Hi all,
> 
> there's been talk. Please correct me if any of this is wrong. Mike
> doesn't want to organise Barncamp 2018. Clara and myself would like
> there to be a Barncamp 2018. To this end we would like to find a way to
> get the project organised in as completely decentralised way as possible.
> 
> Who's in? Who wants to help organise and implement Barncamp 2018? How
> many hours could you put aside and at what times? What could you
> physically bring to the event?
> 
> Also part of the talk has been what organising tool we need to sort this
> out. There's been a suggestion of gitlab, but that's really a tool
> pitched as software development. I'm not keen on that one.
> 
> More generic tools I think might be useful would be Mantis. They are
> still software based, but are good to use for general issue tracking.
> There's also Whups, which is the Horde framework issue tracker which is
> simple and good, and Bugzilla which I think might be over egging the
> pudding.
> 
> So, Mantis is my fave. Happy to install it for people to use. More
> suggestions please.
> 
> So though I would like to stick to non-proprietary tools for
> organisation, I think that using doodle for deciding the date would be
> most efficacious. I'll set one up if nobody objects.
> 
> I've loads more thoughts and idea for next years barncamp, I'd like some
> of us to set up online meetings to have a bit of banter about it.
> 
> Cheers,
> Ben
> 
> 
> 
> 
> LINKS:
> 
> Bugzilla Demo:  https://landfill.bugzilla.org/bugzilla-5.0-branch/
> Horde Demo: http://demo.horde.org/login.php
> Mantis: https://mantisbt.org/bugs/my_view_page.php
> 
> 
> _______________________________________________
> HacktionLab mailing list
> HacktionLab at lists.aktivix.org
> https://lists.aktivix.org/mailman/listinfo/hacktionlab

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <https://lists.aktivix.org/pipermail/hacktionlab/attachments/20171025/ac7fd6e9/attachment.sig>