Meetings/20140812
Time and date
Tuesday 12 August 2014, 6.30 PM UTC. #diaspora-meeting @ FreeNode.
Topics to discuss
Next release
Should we release during the next month?
Community birthday
The 27th of August, the community will have run the project for 2 years. Do we want to do something to celebrate that? (Release: see above, blogpost, ask for community artwork... ?)
Hosting of diasporafoundation.org
- Who should appear in the whois information for diasporafoundation.org?
- Move away from Dreamhost to a platform which supports multiple people having root-access to the domain?
Guidelines for adding agenda items
Do we need guidelines for adding items to this meeting agenda?
- Should only people who have 'voice' in the meeting be able to add agenda items?
- Should the agenda be restricted to certain sorts of topics (i.e. the types of item that can be usefully discussed in these meetings)?
How to warn about known bugs in develop
Sometimes the develop branch contains bug we are aware of (currently the profile photo upload is broken, months ago it was the mentions in the publisher). How can we warn the podmins using the develop branch that there are these bugs, so they don't update their pod?
Docker images
Howto, usage, concept, interest : https://github.com/Chocobozzz/Diaspora-Docker/wiki/How-To
Registry : https://registry.hub.docker.com/u/chocobozzz/diaspora-docker/
User Experience discussions
Given the controversy in tickets like #4657 we should talk about how (or maybe even IF) we want to achieve a consistent UX/UI which is usable for everyone. This point may get extended to a general discussion about the projects goals.
What did we decide?
Next release
next-major is not ready. We triaged the issues for the next-minor milestone, there are only 4 left including 2 pull requests. If we close everything before the next meeting, we will do a minor release, else, we will discuss about it in the next meeting
How to warn about known bugs in develop
Podmins running the develop branch are persons close to the project, they should check github carefully and be aware of the existing issues. But we need to be thoughtful and create issues we are aware of.