Closed Bug 345525 (party2) Opened 18 years ago Closed 18 years ago

Plan Firefox 2.0 Release Parties

Categories

(mozilla.org :: Miscellaneous, task)

Product:
mozilla.org
Component:
Miscellaneous
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: beltzner, Assigned: asa)

References

(
URL
)

Details

Firefox 2 is coming, and a party is required. The release schedule/dates are available at http://wiki.mozilla.org/Firefox2/Schedule
Assignee: mitchell → asa
Alias: party2
We need to resurrect the 1.0 party tool.
I can't remember the version 1 tool - I put something basic together last night at http://mozilla.nachmore.com/party that may be suitable for the time being.
Oren, on first glance, this looks great. Is it cool to announce this at Spread Firefox and get people looking at it? 

Also, are you cool with (have time for) making changes as we get feedback on the tool? Are you open to others hacking on the tool? Would you be willing to donate the tool to Mozilla?
Oren: Great work!

Will you be making the code available, so we don't have to rewrite it again if you get hit by a bus? ;-)

A few thoughts on the implementation:

You need to have a simple username and password system for the party organiser, so they can log in later and update the party details. The version 2 tool had this; without it, people do things like subscribing party_now_at_2pm@mozilla.org to the party to update the info.

Most countries don't have States; if I were you, I'd just have "City" and then a freeform "Location" field.

You need to remind people to put the party time.

You also need to allow people to delete parties, if they are cancelled or people submit them to test the system. Without this feature, I can't test the system :-)

Gerv

Oren, it's cool. It has better open source code to make party tool for future. Also  it can be possible plotting in Google Maps through inputing only address by Geocode API, http://www.google.com/apis/maps/documentation/#Geocoding_Examples.
And please make this tool localizable. 
wow, lots of feedback :) So here goes:

1. announce on sfx: yes. I blogged about it there, but didn't get to much publicity (I reckon not to many people read things that don't get to the main page).

2. making changes. Since I can't work on my SoC project at uni, I can work on a small project like this. Just keep giving me things to do and we'll see how I go with them :)

3. open to other hacking: of course!

4. donate the tool: wow... of course! What do I need to do?

5. code available: asap (i.e. tomorrow)

6. party editing: is done via a password that is sent to the initiator and is valid once he verifies the party. I don't think a project this size needs a centralised user/password base, I doubt that there will be more than one initiator per party anyway. Worst case, the password is user changeable so someone can just set every party of his to the same password.

7. note: registration of false emails is not allowed... all emails are verified before addition to the list.

8. time: whoops! :) Thanks, time has now been added

9. state: not sure about the state thing. It's there still, not compulsory though I can always get rid of it...

10. deletion and cancellation: done.

11. tests: test parties can be submitted to the "Test Parties" country (last on the list).

12. geocoding: done... available during the registration and editing process as a helper feature for the initiator. 

13. localisation: if there will be a support base for this, this will be the next thing implemented.
Donating the tool: you would need to check it in to mozilla.org CVS. Do you have CVS access? If not, this part may have to wait. But occasional publicly-posted source tarballs would be cool. What technologies are you using?

Party editing sounds great.

About the State thing: it's only small, but having State does make the tool look Americentric, and we try and make it obvious that we treat everyone equally. Is there some value in having State as a separate field? Perhaps there is for the US. Are you able to have the State box appear only if USA is chosen?

Localisation is a great idea; ideally, we would minimise the amount of text involved to reduce the burden. So put some l10n infrastructure in place now, but let's not call for localisations until the tool and the text are more finalised.

One more thing: try and make the code generic, and only the skin "Firefox-y", so that other projects could do their own skinning for their own parties.

Gerv
No CVS access as of yet... will get source tarballs worked out.

American centric??? LOL I'm a born and bred aussie ;) So that was why I thought about states... will get rid of it.

Localisation would be nice, i'll see about getting that done asap.

Regarding templates etc. for a more generic project - that's a bit of a todo. I'll work on that tomorrow, most of the code can be split up easily.

The project is currently only php based. Because of a problem with php5 and mysql on my hosts server I can't use mysql, so i've gone for just the basic files approach. This makes some things easier and some things more complex and time consuming. On the other hand it is completely dependency free (apart from php and write access to a data folder).
As long as the performance is OK, basic files is fine. No need to over-engineer.

Gerv
last things for today:

1. state disabled (commented out)
2. view all parties implemented
3. main template seperated from code - still work to do here
4. small buggy stuff cleared up

mid-air collision!

performance right now is fine, though the site is not built for high volume write access (i.e. lots of people trying to create parties at the same time for the same countries is probably going to cause some trouble).
Oren,

I'll be sending you an e-mail soon with details concerning a development arena for you to use. :)
Thanks to the help of Reed & Ryan the scheduler is up and running at http://www.firefoxparty.com .

Regarding privacy, what do people think is the best way of hiding user's emails. On the original MozParty tool the initiator and subsequent participants emails were listed as plain text. Ryan has just implemented a basic email text -> image convertor which displays the email as an image. 

Is there any real reason to display the emails of the people who are coming? Maybe only to the initator under an administrative panel? As for the initiator's email maybe it should just be a name with a link to an email form (email is then sent out by the site and no emails are exposed).

What do people think?
We're looking at the last week of September or the first week of October for party dates. Hopefully we'll be able to nail that down soon but we should launch the tool ASAP with that info and refine the dates as we get closer. 
A horrible bug has just been discovered by one of the party initiators that caused his party to be deleted.

I have now fixed this bug so things should be back on course. I will have more time to work on the final version this weekend, though till then the project is up and running. Everything that is created now will be migrated to the database later on (so nothing should be lost).
Oren: the tool seems to have been disappeared, to be replaced by a "Coming soon" graphic. What's up?

Gerv
funny that you should mention that - I am just asking Ryan exactly the same question. Turns out it was a technical glitch that bumped the precedence of index.html to higher than index.php.

Development still continues on the beta, which is slightly more powerful and is connected to a database. For those who are adventurous development is up at http://www.firefoxparty.com/beta/
Plan of record is to promote this site as the "official" planner, incorporating into SFX and marketing plans to sponsor and promote parties, provide kits, discounts on Mozilla Store, etc.
Oren, Chris: is it OK to start promoting the site, or would you like some more time to work on it?

Gerv
The party tool is not staying at its current location. As soon as Oren feels he is done with it, I'll be checking it into CVS. The server-ops will then set up the necessary infrastructure to run the site at firefoxparty.com (I'll point the nameservers to Mozilla). Until the site is moved to its final location, the tool should not be heavily promoted. It's still in beta phase, afaik.
OK. You need to ask brendan@mozilla.org about where in CVS you should be checking it into. For example, I seem to remember (because I didn't ask about Hendrix, and got told later) that the webtools top-level directory is deprecated in favour of the "tools" directory. So you should check with him.

Gerv
(In reply to comment #21)
> OK. You need to ask brendan@mozilla.org about where in CVS you should be
> checking it into. For example, I seem to remember (because I didn't ask about
> Hendrix, and got told later) that the webtools top-level directory is
> deprecated in favour of the "tools" directory. So you should check with him.

Hmm, I was told by both justin and mconnor that the webtools directory would be fine. New stuff is still being added to webtools. This is a "webtool," not a "tool," so I'm not really sure why it would go into tools. I think of tools as being used for just scripts and stuff that are used in a non-interactive sort of way. However, I will confirm this with brendan on IRC.
> This is a "webtool," not a "tool," so I'm not really 
> sure why it would go into tools.

That was my thought at the time, hence the fact that I remembered what he said. So please do check :-)

Gerv
It has been many years since we tried to deprecate webtools, and myk and I at least have promoted it for web app stuff (php or cgi).  Tradition!

/be
We're live at http://www.firefoxparty.com/. SFx post coming soon. An e-mail will be sent out to all users of the old site requesting them to move to the new site.

If you find any problems with the site, please file a bug under the Webtools :: Party Tool component. Thanks! :)

It's party time!
URL: http://www.spreadfirefox.com/node/24160 → http://www.firefoxparty.com
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
You all rock!!!
You need to log in before you can comment on or make changes to this bug.