hoaproject / actionboard Goto Github PK

We need an administration panel for isso, our comment application.

Scenario

As an administrator, I would like to

• list:
  • comments,
  • threads.
• edit and
• delete comments.

We are going to move our machines in the “cloud” (ouahh). So we have to decide whether we are going for AWS for Azure. Discuss here and explain pros/cos.

Tasks

• Why AWS (@Pierozi)
• Why Azure (@Hywan)

Depends on #3.

Because we love open-source, we don't want to do something only for us, and because doing something public makes it better, we would like to propose the administration panel for isso to isso.

Tasks

• Create an issue to see if they are interested,
• If they are, discuss about the lead and the hosting,
• Finally, promote it.

Hoa virtual meeting : 2016-05-16

Ordre du jour :

• Alexis : communication
• Grummfy : Hoapex
• Ivan : Statut sur Hoa (tout projet confondu)
• Raphaël : compte bancaire
• Ivan : 2 millions downloads

TODO

• Ivan : ajout grummfy en contact github pour recevoir les notifications team
• ? : installation closure pour facilité la communication
• Grummfy : contact maitrepylos pour hoapex
• Ivan : débute le blog post weekly report
• Raphaël : ouverture compte en banque
• Ivan : installer Discourse sur l'infra actuelle

We need to sell goodies. We do not want to host a selling application. We need to find one or many shops online to sell goodies.

Tasks

• Open shops to sell goodies,
• Define at least 1 goody per shop,
• List shops on the website.

In Hoa Apex 3rd edition, we discussed about our needs regarding machines.

We need 2 machines:

1. Web services, mail and search,
2. CI.

I am writing it here for the history.

https://lite6.framapad.org/p/hoaproject_meeting_20160201

Milestones

The following milestones have been closed:

• 2015 October (mid),
• 2015 October (end),
• 2015 December (end).

The following milestone remains opened:

• 2015 November (end).

The following milestone is new:

• 2016 February (end).

Some issues have been moved from existing milestones to the new one.

Recalibrate the amount of work

This system has been designed for the first time during Hoa Apex 3rd edition, and we need to recalibrate the amount of work. Now we have less work to do and better priorities.

Priorities

Top-priorities are:

• Infrastructure (https://github.com/hoaproject/Infrastructure),
• Enhanced README.md and use them when documentation is not written yet (#17).

What about the future?

Regarding source code, we continue to work on existing issues, such as:

• Migrating test suites,
• Writing more documentations,
• Having around 15/20 in progress issues in https://waffle.io/hoaproject/central.

Regarding the foundation, we need:

• To finalize the bank account,
• Open subscriptions,
• Design new products.

Regarding the project organization, we decided to:

• Continue this kind of meeting every month,
• Organize the next Hoa Apex edition in Belgium!

This card are for goal to have an Aws dedicated account for Hoa Organisation.

• Create a master dedicated account
• Create one user for each system administrators
• Settings IAM & Roles for Server Mail / DB
• Settings IAM & Roles for Server Web & PHP

We have to define a backup strategy. So far, this is not clear and it changes often.

Tasks

• Define a backup strategy.

Depends on #2.

IRC logger has to be deployed in our infrastructure.

Tasks

• Install logger and connect it to #hoaproject,
• Make logs available through the website.

We need to restore mailing-lists and mails services.

Mails belong to the “infrastructure” label and mailing-lists belong to the “service” label.

Tasks

• Restore mails,
• Restore mailing-lists.

Depends on #3.

During Hoa Apex 3rd edition, @camael24 and Cyrano proposed themselves as moderators. I agree with that.

However, Cyrano needs a Github account.

Tasks

• @camael24, please, could you ask Cyrano to create a Github account?
• When done, we must include it in the @hoaproject/hoackers team.

We need a bank account for the foundation.

Tasks

• Open a bank account for the foundation,
• Get a credit card,
• Get online listings and actions.

We need to update the #hoaproject IRC channel topic to mention its logged and provide a link to the botbotme page (https://botbot.me/freenode/hoaproject/). The URL can be shortened. This is required by Freenode terms of service.

Depends on #7.

A notification ML is needed to spread “events” in a centralized way. This is a technical ML, for the infrastructure, CI etc., not a “public” one.

Tasks

• Create the [email protected] ML.

Agenda

1. @Hywan: Numbers and news,
2. @Grummfy: Hoa Apex 4th edition,
3. @osaris: Bank account,
4. @Hywan: Discourse,
5. @Pierozi: Infrastructure,
6. @vonglasow: PHP 7.1,
7. @vonglasow: New flyers for Hoa, designed by BrandBrothers,
8. @Hywan: New fashion is to blame dependencies.

Meeting

Numbers and news

We record 2,650,816 installations on Packagist.
We record 1732 stargazers and 606 forks on Github.

Discourse is a new sponsor! Hurray!

New baby in the hoackers, that's so great!

Hoa Apex 4th edition

2 possibilities. Either we join a big event (also organized by the guys who are organizing the next Hoa Apex, namely @Grummfy and @maitrepylos) or we keep it as usual. In the former case, the event could be delayed. In the latter case, we could schedule the event for November.

Maybe this is too early. We need time to find sponsors for the food, to find good transport fees etc.

Location: Bruxelles or Namur (Belgium). Confirmed!

Bank account

This is a difficult topic. The fundation is French, with French laws, but the president is a french leaving in Switzerland, and the treasurer is a swiss leaving in Switzerland.

Classical banks do not want us. We need another bank. We are trying N26.com (ex number26). Internally, they are changing a lot, which postpone their opening in Switzerland. We are patient and we are waiting. We are waiting since almost 1.5 years so we can still wait few months.

Discourse

Our mail server (including mailing list) has been removed due to innatention few months ago. This is hard to restore.
Our comment system (http://posativ.org/isso/) is cool but we do not have an administration panel. We tried to develop one hoaproject/W3#57.
Some people complained about mailing list.

We talk to Discourse and they have accepted to host an instance of Discourse for us! Hurray! Accessible at discourse.hoa-project.net. Under configuration. They are 4 administrators so far with 4 moderators. We are currently working on the setup.

We will replace our comment system by Discourse too.

We will publish a blog post when it will fully configured and usable.

We are so happy to finally have a new platform to exchange.

Maybe we will host our own instance in the future. Currently we don't because our machines are not powerful enough (https://www.scaleway.com/).

Infrastructure

We have a big project, called Infrastructure (https://github.com/hoaproject/Infrastructure). The goal is to fully automate our infrastructure, from VM to services.

After months of work, we face two issues:

1. This is a huge project,
2. The goal was to setup the CI and the mails, and it's still not here.

Having something under development in not a solution. We need a CI. We need mails. The other services are working (Git, HTTP, SSH, databases etc.).

Long discussion about our goals and short-term needs.

Solutions: We should use our AWS instances with AWS tools. Then automate things slowly. Step by step, instead of addressing the whole thing in a single step. For the CI, we will maintain all the scripts for Travis. For the mails, we have Discourse to replace mailing lists and Gandi to replace mails, so it's fine.

Infrastructure is not dead. It will evolve to something a little bit different. Current landing code is working great.

PHP 7.1

PHP 7.1 is in beta. There is some BC breaks we have to catch. 2 majors yet:

1. PHP identifiers are changing, hoaproject/Consistency#12,
2. void is a new keyword, hoaproject/Consistency#10.

We are using atoum for the unit test framework behind Hoa\Test. This issue atoum/atoum#615 is blocking. We have to fix it too.

Flyers

BrandBrothers (http://brandbrothers.fr/) is the company behind our new logo. They are offering us to design flyers, in case of events or files. This is an excellent offer, thanks! Go!

New fashion is to blame dependencies

Hoa's libraries have smart dependencies. Small ones, addressing the SOLID principle, with a high quality and safety. However, the new fashion is to blame project with several dependencies and to promote project with zero or few dependencies.

What people see with Hoa is 4-5 dependencies per libraries. This is true. 1 dependency = few files. What some people would prefer is 1 dependency per library, so 1 dependency = many files. This is just a perception; We are not going to change that.

However, we must communicate about our design and why this is smart to have small and reusable dependencies (it reduces the bug surface, reuse the code so upgrade performances etc.).

If this is justify and clarify, no worry.

Goals for the coming month

@Hywan:

• #26 (comment).

@osaris:

• #26 (comment).

@vonglasow:

• #26 (comment).

@Grummfy:

• #26 (comment).

@Pierozi:

• #26 (comment).

We need a “foundation application” to manage the list of subscriptions, cotisations & co.: All the services around a foundation.

Both a heavy application or a web-application are acceptable. Only constraints: Being open-source.

Tasks

• Find a “foundation application”.

Here is the answer about the stats of waffle : https://github.com/waffleio/waffle.io/issues/2110#issuecomment-145686222

we made the decision during Hoa Apex'15 to use an IRC logger to keep track of discussions, and have the ability to search through them.

the logger must have these features:

• be light
• be robust
• offer a web IHM
• the web IHM must be searchable
• do some mail obfuscation

Criterias

These questions are some points that can be used as a basis for our choice. This is not an exhaustive list.

• does the logger obfuscates mails?
• can we have only log features?
• is there a way to have not logged messages (with something like [OFF] this message is not logged)?
• if it is a hosted service
• Is it open source?
• can we download an archive of the logs in an exploitable format (in case we want to leave the service)?
• can we ask for some logs deletion? (imagine we put a password in the chan by mistake)
• if it is a self-hosted service
• what are the system requirements?
• what level of administration is required?

Tasks

• compare loggers
• choose one of them

https://lite6.framapad.org/p/hoaproject_meeting_20160303

People present to the meeting (https://meet.jit.si/hoaproject)

• Ashgenesis
• Raphael
• Thehawk (Julien)
• Metalaka

Regarding source code, we continue to work on existing issues, such as:

• Migrating test suites,
• Writing more documentations,
• Having around 15/20 in progress issues in https://waffle.io/hoaproject/central.

Regarding the foundation, we need:

• To finalize the bank account : Raphael ping the contact,
• Open subscriptions : we are waiting for the bank account,
• Design new products: Thehawk suggest a mousepad, Raphael think we don't need new product for the moment.

Regarding Hoa Apex 16, we decided :

• To wait for the belgians participant to attend a virtual meeting to start the organization.

Goals for April

• Raphael : fix at least 1 issues on 3 open,
• TheHawk : admin isso implement answer from backend,
• Metalaka : Flex Entity need a name & hoaproject/Websocket#58
• Ashgenesis : status infra + clean issues.
• Maitrepylos: Continue to fill the todo http://wiki.hoa-project.net/projects:central:todo

Next meeting scheduled on April 4th or 8th, a framadate will be created soon.

Our goal is to get new machines up and running with at least 1 service online shortly.

Tasks

• New machines online with at least 1 service online.

according to https://framasphere.org/posts/1161033, there is

• HashOver
• jskomment
• Commentics

Our search service is based on ElasticSearch. This application likes to eat memory. We need to optimize it.

Original author of ES instance: @GuillaumeDievart.

Tasks

• Optimize ElasticSearch resources.

We need enhanced README.md for each library (with more information in it).
We also need to use README.md when the documentation is not written yet.

Tasks

• Enhance README.md,
• Use README.md instead of documentation when this latter is not written yet.