Choice of stack
Hugi Ásgeirsson
Public
Seen by 20
What stack should we use? Based on the concept and the requirements, what would fit us best? Developer skills and feasibility of developing an MVP quickly, as well as ease of maintenance as a community open source project should all be factors that we take into account.
To get us started, here are a few stacks that have been discussed:
* React, Meteor, MongoDB
* React, Meteor, Neo4j
* React, GraphQL, Relay (or Apollo), MongoDB
* React, GraphQL, Relay (or Apollo), Neo4j
What do you think? What would be a good fit for us?
Gustav Larsson Tue 5 Dec 2017 6:37PM
I think it makes a lot of sense with a mono-repo in this case, as we could then utilize GitHub's issue tracker in one single place if we'd like to (might be an alternative to Trello?).
Eslint would be great! The Airbnb configuration sounds good to me.
I agree that Slack or any other real-time chat would be nice also! I really like Slack but a good alternative could be Gitter which is more open (open sourced, all conversations public, anyone can join)
Erik Frisk Tue 5 Dec 2017 6:53PM
Good call! I agree that Gitter is better for us and we could start with just GitHub issues for to-dos. Less visual but definitely nice to have everything in one place. If it gets too unwieldy we can always set up a Trello board later.
Poll Created Tue 5 Dec 2017 3:28PM
Collaboration on boilerplate for Realities Closed Fri 8 Dec 2017 3:11PM
@erikfrisk has set up a boilerplate repository following a decision that anyone who wanted to could set up a repo and start building based on the requirements in the whitepaper.
He's asking for collaborators.
Check the repo here: https://github.com/erikfrisk/realities
Tag Erik with your GitHub account for access.
Results
| Results | Option | % of points | Points | Mean | Voters | ||
|---|---|---|---|---|---|---|---|
|
|
Yes, I can put in some time this week | 80.0% | 4 | 0.8 | 5 | ||
|
|
I'll work on the project after the Hackathon | 20.0% | 1 | 0.2 | 5 | ||
| I can't put in time this week, but I'll come this weekend | 0.0% | 0 | 0.0 | 5 | |||
| Undecided | 0% | 0 | 0 | 16 |
5 of 21 people have participated (23%)
Vlad Mickevic Tue 5 Dec 2017 6:24PM
Can you also add me? github username “vlamic” and email for trello: [email protected]. Thanks!
Erik Frisk Tue 5 Dec 2017 6:28PM
@vladmickevic Added you to the repo!
Erik Frisk Tue 5 Dec 2017 7:04PM
We have a Gitter! https://gitter.im/realities
Hugi Ásgeirsson Tue 5 Dec 2017 10:29PM
Yeah, git actually has a really great built in Trello clone that integrates with issues, forgot about that! Check it: https://github.com/erikfrisk/realities/projects/1
Hugi Ásgeirsson Wed 6 Dec 2017 2:59PM
What we went with (or rather what I suggested) was that since the person building the boilerplate needs to be familiar with the stack, anyone who could put time into building a boilerplate following requirements could define a stack and start working. Erik did, using React, Next, Apollo/GraphQL. So since it was a decision we left up to doocracy, it’s kind of still a decision in process. But it’s probably time soon to run a Loomio decision on the architecture in a wider sense - both with regards to stack and what I’ve started sketching here: https://www.loomio.org/d/trRnp3wA/project-architecture-and-boilerplate-development
As for Neo4j, I’d love to use it, but since Erik might not have time to learn it, someone else would have to give him a hand and define what he’s started working on with Neo4j rather than Mongo. Good news is that this should not be hard - Apollo and Neo4j are supposed to go hand in glove. Feeling up for syncing with @erikfrisk and start working on DB @matthewparsons ?
Erik Frisk Wed 6 Dec 2017 3:34PM
I've watched a couple of YouTube videos on Neo4j and it doesn't look too difficult to get started. I still haven't added a database to the boilerplate, so feel free to dig in and add it @matthewparsons.
Erik Frisk · Tue 5 Dec 2017 4:56PM
PS. We could also use a channel in the Borderland Slack group.