< Distribution | FreeMedia
Problem 1
Keeping the form open for different durations. NA has more contributor, the form should accept NA requests for 15 days. APAC has less contributors. The form should stop accepting requests for APAC after a couple of days.
Solution 1: Multiple form for different regions.
Observation: Managing so many forms are going to be pain. Have to login to puppet everytime. Have to update all the forms by hand.
Solution 2: Having a wiki variable and pulling that in.
Observation: Anyone can edit the wiki. Will have to keep a very close watch. We want to separate the admin tasks.
Alternate solution 2: https://fedorahosted.org/freemedia/ Has a wiki that not everyone can edit.
Problem 2
Keeping a tab on vendors.
We have ~200 Vendors as off now. We don't need to show all the information to everyone. We need to show region specific shops to the prospective buyers. It can only be done using geoip. There may be a list at the top for finding the vendor. But, it would be unwise to leave it to the user. They will give up very soon and request a freemedia.
There will be problem of maintaining a list. One have to delete the vendors by hand from wiki. If it comes back later, it will have to be reinserted.
Also, enrolling and removing vendors need wiki edits. The ideal workflow should be a form, which upon submission by vendor, notifies the admins and who in turn approves/rejects the listing requests
problem 3
Wiki Table is easily breakable. Manual edits *do* break long tables. It is not possible to maintain a nice list in wiki.
Also, the wiki tables are not the best examples of presentation.
Problem 4
Integration problem. How do we show a user all the available options for getting a disk at one place and without being clumsy?
We also need to have a central admin point from where we can do all the admin stuff.
Problem 5
All the admins does not have access to infrastructure. How do we enable them to administrate the stuff without logging into puppet?
Problem 6
Maintaining a up-to-date price listing and alive shops. I still have no clue how to do this.
Problem 7
Keeping tab on contributors who are not accepting requests.