lorddev / applifry Goto Github PK

Need the simplest possible scoring system for phase 0, to be expanded in future versions.

Ideas

Points for showing up

1. You get a point for signing in with Open ID.
2. You get 2 points if you have a Gravatar.
3. 10 points for adding your first idea.
4. You get 20 points for adding a new company with a verifiable website. (Subdomains don't count, sorry.)
5. 10 points if you're on Github
6. 15 points if your project is on Github and public (at idea creation or if added after the fact)
7. One point per field edit per idea per day. (So you can't go and input your idea one letter at a time to score more points.)
8. One point per day simply for visiting the site. Doubles after a week of consecutive visits, but goes back to one if you skip a day.
9. 10 points for one-month anniversary provided you visited the site within the last 15 days.
10. 20 points for six-month anniversary provided you visited the site within the previous month.
11. 50 points per annual anniversary provided you visited the site within the previous month.

Community reputation points

1. 100 points if an idea you created is accepted. Permanent 110% weighting if your idea is implemented as open-source.
2. 2 points per upvote on an idea
3. 1 point for up voting an idea
4. 1 point when a comment you make or a feature you branch is upvoted.

These are just initial thoughts. A feature request will be added on Applifry for fine-tuning.

Use the GitHub API to attach an Issue from a developer's existing repo to an Applifry proposal. Should be able to attach at the main proposal level, or at individual feature requirements level.

Pen & ink design like App Machine logo but pedal-based

Suggested by @swsenterprises: Reduce word count on applifry.org to 100. Leave the details for the wiki.

This gets the project off the ground, since it's technically usable at this point.

Either a "donate" button, or a link, or an actual Express Checkout implementation in case people want to help pay for hosting fees, etc.

In order to start off with something that works, issue #7 was created to do a simple insert operation.

Plans for the issue editor are that instead of a <textarea /> it should be an html5 <section /> tag with contenteditable="true", which would allow us to wrap content with spans for highlighting, striking out, generating feature/comment threads, etc.

A simple example is that a user could highlight a "cool feature" section and upvote it. This is my idea for the core of the app. Once it's in place we can utilize the app's own feedback features for fine-tuning it.

Just a simple start page to get the project started.

Take the freehand text we're using for graphics and turn into a web font that we can use.

(Until then, use http://www.google.com/webfonts/specimen/Architects+Daughter)

Simple form to input an idea. Associate with user's open-id.

Add license to README

Add references to GitHub Facebook .NET SDK.

We may end up altering and issuing pull requests if necessary.

Markdown support for entered text.

Start with a version for each platform right from the start. This includes Android, iOS, Windows 8 apps.

Instead of app-generation tools, write the code in parallel, native for each platform.

Implications:

• Treat version numbers accordingly. For example, Chrome has different version numbers for different platforms (edit: I don't think this is the case anymore), Evernote as well (they just released Evernote 5 for Mac)
• For domain logic, Use the same class names and methods for each platform and make sure domain-layer bugs are addresses on all platforms.

(Need $99 for Apple Dev fees, but can test on simulator first.)

Use Gravitar for user avitars.