search

fossevents / fossevents.in

Upcoming fossvents.in website
https://www.fossevents.in
MIT License
15 stars 23 forks source link

Release 0.1.0 #1

Open theskumar opened 9 years ago

theskumar commented 9 years ago

Goal:

Initial working release of foss events website.

Release Manager : @satyaakam

References

bhanuvrat commented 9 years ago

whats up with this thing? @theskumar

vrdhn commented 9 years ago

I think step 1 is to figure out how to store the posts, and step 2 is commenting system

Support you decide put posts in a database, then you've to build a flow ( submit-review-approval) kind of functionality in the system. On the other hand, if you keep the content as a bunch of markdown files, in a github repo, than you can use existing pullrequest/approve system.

Next thing is the comment system, do you want one at all ? Do you just want to use disqus, or add something of your own ?

If you choose disqus, and md content, it all becomes a static site which is published automatically on approval of pull request. -Vardhan

satyaakam commented 9 years ago

I've added link to vision document in the reference.

theskumar commented 9 years ago

Hi @vrdhn,

Thanks for you feedbacks. Please find replies inline!

Support you decide put posts in a database, then you've to build a flow ( submit-review-approval) kind of functionality in the system. On the other hand, if you keep the content as a bunch of markdown files, in a github repo, than you can use existing pullrequest/approve system.

The concept of PR is pretty good. The only issue with pull request system is that not everyone wanting to post a listing on the website will be technically sound to understand the PR system.

We are deciding to go with database as storage system and use Django framework for admin/database/email need. The idea is to build an interface, which will look/work sort of in way hackernews work and make posting the listing as easy as possible.

Submit/review/approval process

  1. There will an open form with name, description, submitter_email, event_date as compulsory fields.
  2. When a submission is received, email with all the details along with a url to moderate this particular listing will be sent to all the moderators.
  3. Clicking on link will open an authorised page, where moderator can approve/reject or write a note. Email will be sent to all the associated parties.
  4. Once approved the listing will be public on the website with disqus as commenting system.
  5. Further, we will also send an obfuscated link to submitter which will also allow him to edit the listing.

PS: There won't be any registration for event submitter or any public entity. Only time someone might need to register is when they want to write a comment. Someone who wants to be a moderator, will need to fill up a form on website and it will be approved by existing moderators.

Next thing is the comment system, do you want one at all ? Do you just want to use disqus, or add something of your own ?

Let's go with Disqus, as it will make this decoupled and offload many of the commenting related tasks.

theskumar commented 9 years ago

I'm adding the initial blueprints for event list and detail page for discussion:

1.0 Event Listings 1 0-event-list

2.0 Event Detail 2 0-event-detail

Link to source file: https://www.dropbox.com/s/gs8qiaym8u6vmgj/source.ai?dl=0

jainmickey commented 8 years ago

List of pending tasks:

theskumar commented 8 years ago

Thanks updated the main description of the issues as well.