Restarting development

[kamicut]

@chaficnajjar I recently saw activity on the repo. I was wondering if we should throw around some ideas to modernize the code. Notably, I think that relying on a google spreadsheet is very brittle and we can do better (cf #5). Prose recently released a CSV editor so that could be a start, we could host the data on Github next to the code. This would allow outside contributions (however contributors need a github account).

@jessdheere @MohamadNajem if you have some thoughts, maybe you can add to the conversation.

[chaficnajjar]

@kamicut I just tried out Prose and it seems to work. Like you said, let's go with Prose and host the data on Github instead of relying on Google Sheets.

[jessdheere]

Don't have much to add on the technical level, but given recent political
movement in the country, I'm hearing people talk about preparing for
elections. Maybe we should play with ideas for what we could do to update
Nouwweb? We also have a new space in Badaro where we could easily host
hacking happy hours etc. We're up for whatever. Maybe we could have a call
soon to brainstorm?

BTW, we are also working on new, cleaner version of http://smex.silk.co.
@kamicut and @chaficnajjar would love to share with you where we're going
and get your ideas!

jd

On Tue, Sep 27, 2016 at 5:05 AM, Chafic Najjar [email protected]
wrote:

@kamicut https://github.com/kamicut I just tried out Prose and it seems
to work. Like you said, let's go with Prose and host the data on Github
instead of relying on Google Sheets.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#7 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGcgSxg1Ow9PVOul5l_spkjTO8V_3I1uks5quHnYgaJpZM4KGmvA
.

Jessica Dheere
+961 76 717 664 LEBANON
+1 347 694 7639 From Anywhere

[kamicut]

@jessdheere sounds good. At developmentseed I've been building an alternative to the excel method for entering data and updating an API:

Method 1: Unauthenticated users update to a form, they're submitted as pull requests to this site and manually merged in. Once an update is reviewed and merged in, a process updates the API.
Pros: can accept outside contributions
Cons: susceptible to spam, someone has to actively review the changes

Method 2: Authenticated users (not just github, but can be a whitelist of emails) have access to a form, and edits automatically update the API.
Pros: all data is validated because of authentication
Cons: outside contributors would need another way to enter data if they have it

Which do you think would be better for keeping this data updated?

I'd love to chat about new stuff we can add to this, or openleb.io to keep it going. It will have to be after election day though, things are pretty hectic here 😛

[chaficnajjar]

@kamicut I think it would be really useful to allow both authenticated users (edit form -> automatically update API) and unauthenticated users (edit form -> automatically send a pull request) to update the data. I would say we do both methods. Also, I don't think spam from unauthenticated users will happen often.

@jessdheere @kamicut I also think we should chat about all of this. What do you prefer we use: Slack? Skype? Hangouts? Something else?

[kamicut]

I recently came across a few technologies that would make this much simpler to redevelop. Let me know if you're still interested in this.

[chaficnajjar]

@kamicut Between work and side projects, I'm afraid I won't have the time to dedicate to this project. I'll keep an eye on this repository though. Thanks for pinging me about this.