Closed Bug 598917 Opened 15 years ago Closed 13 years ago

Migrate mozilla.status.net to social.mozilla.org

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task, P5)

Product:
Infrastructure & Operations Graveyard
Component:
WebOps: Other
Platform:
x86
macOS
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: paul, Unassigned)

References

(
URL
)

Details

(Whiteboard: [triaged 20120824])

Hello, Can we put the domain status.mozilla.net into service and forward requests to mozilla.status.net? If we then promote status.mozilla.net we would be able to easily migrate away from status.net hosting in the future and host the site at Mozilla. Best, Paul Booker Appcoast
Summary: Question for the hostmaster. → Question for the hostmaster
After reading the Websites Taskforce Proposals another possibility for the site URI could be status.mozilla.org however i think status.mozilla.net is the coolest option and we could probably use this domain further for emerging social frameworks that were building like Batucada & SudoSocial https://wiki.mozilla.org/Websites/Taskforce/Proposals/Domain_Name_Strategy#Proposed_URL_Changes Best, Paul
Can anyone suggest who best to assign this bug to ?
Can we put the domain status.mozilla.net into service and forward requests to mozilla.status.net? Best, Paul
If anyone can advise who to assign this bug to or who i should CC here in order to get some feedback quickly i would really appreciate the help. FYI mozilla.net is a domain that is being used on the web .. http://videos-cdn.mozilla.net/serv/firefox4beta/ants/FlightDemo.webm [enjoy] Best, Paul
David: could you help Paul sort this through? Seems like a good idea. You're the expert in how all this should fit into the naming and web universe.
Thanks Mark.
Sure, happy to help. From earlier discussions with mrz, I don't believe mozilla.net is available for public uses. Apparently mozilla.net is reserved for the heavy-lifting infrastructure (load balancers, download servers...) and using the domain for a public site would introduce security and performance issues we don't want. Not to mention that mozilla.net doesn't fit in with the new domain name strategy. As mentioned in comment #1, status.mozilla.org would be a better fit since we're trying to move to using mozilla.org for all public-facing Mozilla sites. Could you provide more information about the downsides you see with using status.mozilla.org and we can try to address those issues?
Summary: Question for the hostmaster → Sort out Mozilla domain name to use for current mozilla.status.net site
Thanks for your help David & appreciate the quick response. The domain status.mozilla.org sounds perfect for us. Shall we go ahead and put this domain into service for mozilla.status.net ? Best, Paul Booker
Glad to hear status.mozilla.org will work. As for putting that into service, that would need to be addressed by someone in IT -- I can't speak for their process of migrating existing sites to our servers. You could move this to product:mozilla.org, component: server operations for further discussion.
David, When i change the "product" to mozilla.org the "component" is not repopulated with the corresponding list of items. Any ideas?
Re comment #10, it doesn't repopulate dynamically. If you submit after picking the new product, you'll have a chance to pick the new component after that.
Assignee: nobody → server-ops
Component: mozilla.status.net → Server Operations
Product: Websites → mozilla.org
QA Contact: mozilla-status-net → mrz
Version: unspecified → other
Summary: Sort out Mozilla domain name to use for current mozilla.status.net site → Migrate mozilla.status.net to status.mozilla.org
Your hostname sounds confusing since http://status.mozilla.com/ already exists.
Were open to suggestions for the domain name, another possibility might be updates.mozilla.org or notices.mozilla.org
(In reply to comment #13) > Were open to suggestions for the domain name, another possibility might be > > updates.mozilla.org or notices.mozilla.org What’s the likely usage of the statusnet install, mozilla community & developers talking about developments? service downtime? Remember that users will be @something@updates.mozilla.org, does updates. still fit?
The site exists primarily so that our mozilla community can post notices about what is happening within Mozilla and anything related to it's mission to keep the web open for everyone. Just getting some further feedback from Jamey [project lead] , i'll reply shortly. Best, Paul Booker
I wasn't familiar with status.mozilla.com. Glad to hear other domain names could work for this. Unfortunately, update.mozilla.org is taken (it redirects to addons.mozilla.org for historical reasons) and updates.mozilla.org is probably too close to that. It sounds like notices.mozilla.org could fit. Brainstorming some other ideas: * timeline.mozilla.org * social.mozilla.org * micro.mozilla.org * statusnet.mozilla.org
I personally like social.mozilla.org
my vote is social.mozilla.org
The votes are in and have been counted the winner is .. [a pause to build up the tension] .. social.mozilla.org :-) Shall we set up social.mozilla.org so that initially it forwards requests to mozilla.status.net? We can then have a conversation about migrating the site to Mozilla. Thanks for everyone's help. Best, Paul Booker
Summary: Migrate mozilla.status.net to status.mozilla.org → Migrate mozilla.status.net to social.mozilla.org
Any update on setting up social.mozilla.org? Could we also look at setting up a stage server in the near future so that we can more easily develop the site with the Mozilla community. Our plugin / theme are currently up on Github https://github.com/paulbooker/mozilla-SN---Plugin https://github.com/paulbooker/mozilla-SN---Theme Best, Paul Booker Appcoast
hi their I also like te idea for social.mozilla.org
Assignee: server-ops → mrz
@Matthew Thanks for stepping up to the plate & helping us get started. If you need me this evening (UK) i'll be IRC in the Social chatroom (just me ;-)) Best, Paul
Paul, after talking about this some more with a few people I think we need to hold off on moving the site for a bit while we discuss the use of social.mozilla.org with more people since it's a high profile domain. For instance, I don't know if any other groups already have plans to use that. I think this wouldn't be as much of an issue on another domain like statusnet.mozilla.org though, so one option would be to review the list of alternate domains that we were considering earlier. If you do want to move forward with social.mozilla.org, let's talk more about how to move forward.
Hi David. Can we explore the possibility of moving forward with social.mozilla.org or something like social.mozilla.org/status Please take all the time you need to discuss with your colleagues. Best, Paul
Paul, just wanted to let you know we haven't forgotten about this. It's just hard to talk to a bunch of people about this right now with the launch coming up. We should be able to get more information about this after Firefox 4 is out.
No worries David, thanks for keeping us in the picture. /Paul
Assignee: mrz → nobody
Component: Server Operations → Server Operations: Projects
David, Any further developments? Best, Paul Booker Appcoast
From IT's side, this is stalled more on site theming and security review.
I think the next step is to discuss this at the next website taskforce meeting on April 21. https://wiki.mozilla.org/Websites/Taskforce/2011_04_21 There seems to be a general need for creating a way for people to experiment with new sites and to get the community to try those sites out without having them presented as official production-level Mozilla sites. Or to put it another way, I could see presenting this statusnet site as a Beta Mozilla site to see if this is useful for the community. If there is good feedback and usage we could then devote the resources to go through the process making this an official site on the mozilla.org domain. Ozten and Ryan are thinking through this as well so I'm copying them to get their ideas for moving forward.
> .. I could see presenting this statusnet site as a Beta > Mozilla site to see if this is useful for the community. If there is good > feedback and usage we could then devote the resources to go through the process > making this an official site on the mozilla.org domain. Thanks David. This sounds like the right directon to go. I think if we work together to further promote / develop the platform on mozilla.org the project will have a good chance of succeeding . > > Ozten and Ryan are thinking through this as well so I'm copying them to get > their ideas for moving forward. Brilliant! Let's plant a new flag on mozilla.org that says we want to keep the *social* web open and distributed :-)
(In reply to comment #0) What are the issues with the current status.net hosting? What is the problem and goals for moving to a Mozilla sub-domain? (In reply to comment #30) > I think if we work together to further promote / develop the platform on mozilla.org the project will have a good chance of succeeding. David's suggestion about a Beta side would involve you or status.net continuing to host the website; this label would help clarify MoCo's responsibilities around the beta. Once proven successful and indispensable to MoFo or MoCo then a team would put the app migration to a mozilla.org sub-domain on to their quarterly goals. Hosting social.mozilla.org would require the StatusNet code go through * Legal and Privacy Review * Security Review * Engagement Review (templates and graphics) * Webdev or Services Review (depending on which team would be responsible for maintaining the codebase) It sounds like a lot of overhead, but we want to make sure projects are sustainable by MoCo's limited resources and that we aren't putting our community at risk. Internal and external projects go through this level of scrutiny. The Taskforce meeting will be good to discuss how we can fix these issues. Documenting your experience and problems with the current situation would really help! Thanks Paul.
(In reply to comment #31) > (In reply to comment #0) > > What are the issues with the current status.net hosting? What is the problem > and goals for moving to a Mozilla sub-domain? The hosting provided by status.net has been working well for a while now as our needs have been moderate but if were going to develop the site further were going to need a stage server, bug tracker, .. if all of these services can't be provided at Mozilla i will be happy to provide these services again leaving production at status.net. My thinking with regards to having a mozilla sub-domain was that we could start using this domain right away and later when we migrate to Mozilla or to my own servers we can then easily migrate our services, Reading ahead it sounds as though one way to move forward with development / promotion of the site is to 1. secure a .mozilla.org domain 2. help us to promote the beta site through your channels 3. continue with our free hosting provided to us by status.net cloud hosting and 4. provide all other services (stage, basecamp, tracker,..) on my own servers Best, Paul
Just a friendly nudge :-) If you have any reservations here or you have reached a decision that you might feel is not what i may have hoped for feel free to speak your mind, some you win some you lose. Thanks for everyone's time on this. Best, Paul
Hi Paul, I know it's frustrating to be in limbo on an answer. (In reply to comment #33) > If you have any reservations here or you have reached a decision that you might > feel is not what i may have hoped for feel free to speak your mind, some you > win some you lose. I don't think any person or secret group has made a decision, it is just that Mozilla would have to make an organizational commitment to move this forward; all the teams that would touch this, are currently swamped with other initiatives.
Hey Austen, Not frustrated at all. We can look into this later in the year. Thanks for getting back to me :-) Best, Paul
Paul, just to follow up on Austin's comment -- things have just been very busy and I apologize for not getting back to you sooner. I'd suggest coming to the next task force meeting and having a discussion there about the process of moving sites to the mozilla.org domain. https://wiki.mozilla.org/Websites/Taskforce/2011_06_02
Thanks David.
Can we nix this request as-is and opt for a Mozilla-hosted installation of status.net software? We could probably set something up in dev/stage this Q and have it put on infrasec's plate for first of Q1.
Corey, that sounds like a great way forward. At present our open social offerings are distributed over mozilla.status.net / identi.ca / .. It would be great if we could combine our efforts. We will also need to work out who will manage the various mozilla @user(s) and !group(s). Probably the best person to own any particular @user would be the corresponding user on Twitter, we could then set up a Twitter bridge so that a post for a given @user on our mozilla site results automatically in a tweet for that @user. Then we will be in control of our social presence on the web and showcasing best practices. Currently I am following the Planet Mozilla fire hose for the about:mozilla weekly newsletter and a number of feeds that are associated with open (social) web that I have been aggregating on i < 3 theopenweb so I'll be happy to help out with managing any number of @user(s) / !group(s). Also I have some experience writing plugins and managing the software on the server so would be happy to contribute time here also. Best, -- Paul Booker ----------------------------------------- https://mozillians.org/u/6a5a5f9929 https://wiki.mozilla.org/User:paulbooker
Hi Corey, .. Any thoughts on moving forward with hosting the site at Mozilla? Should we decide on a domain name to use so that we could start using this domain name before the migration? When we have the site running on Mozilla servers we can fix the *darn* Twitter bridge and work with Mozilla tweeters to support the federated social web. http://paulbooker.co.uk/blog/are-we-federating Best, Paul
would the mozillians list be the right place to discuss this? Also is this a good candidate for community IT, or will this be Mozilla run?
Hi Lucy, I think having either the site hosted at Mozilla or hosted with dedicated hosting provided my Mozilla would be great. Thanks for the feedback. // Paul
Mozilla IT won't have time to handle this in Q1 so this is a perfect candidate for Community IT.
Thanks Matthew, I'll get in touch with Mozilla IT.
Sorry, Community IT :-)
Snagging this... it appears to be a pretty straightforward PHP/MySQL web app, could very likely go onto the genericrhel6 cluster in PHX1. Also flagging this for sec-review, although perhaps a separate bug is more appropriate for that. The code is available here: http://status.net/wiki/Download#Download. We can set up a dev instance for security review, if that helps.
Assignee: nobody → server-ops-webops
Component: Server Operations: Projects → Server Operations: Web Operations
Flags: sec-review?
QA Contact: mrz → cshields
Whiteboard: [pending triage]
crikey this just bug just came back from deep-freeze ;) @Paul any imput?
@jakem: it is fine to flag the bug for review, if we need to do one we will open a separate bug for that work
Priority: -- → P4
Whiteboard: [pending triage] → [triaged 20120824]
I think this project is essentially dead. All of my accounts and notices have been deleted as they have been also on http://social.mozilla.org.uk/. Hopefully someone else will give this idea another go. I still think Mozilla should have a strong presence on the federated social web and encourage other to do so likewise. Big thank you to Ian who supported my work on https://mozilla.status.net/ financially for the 2 -3 years that I worked on the project. Paul
Is this actually dead? If so, we will remove the security review flag next week and someone can close the bug.
It would be very nice for someone inside Mozilla to take it up though, with recent Twitter API policy changes, being a champion of some federated µblogging seems right up Mozilla’s street.
(In reply to John Drinkwater (:beta) from comment #51) > It would be very nice for someone inside Mozilla to take it up though, with > recent Twitter API policy changes, being a champion of some federated > µblogging seems right up Mozilla’s street. +1 I guess the end game for Mozilla should be to build their own application that will provide the community with another way of joining the federated social web. To get started we need evangelists to educate the community of the importance of the federated social web and developers to begin work on building a federated social web application and everyone who is interested in the federated social web working to get involved with standards at W3C. I think it could be a really great Mozilla project. Best, Paul
I don't think this is all that dead... at least, the core code appears to still be getting regular maintenance, and there are still occasional posts to mozilla.status.net. If we were to bring this in-house and advertise it as a "public yammer instance" of sorts, I think it might be a valuable app. Can we still get a secreview of the core code? I'd be interested in setting up a test instance, and judging by the cyclical anti-yammer feedback we get regularly, I suspect there's be a decent groundswell of support. Double-plus-awesome if authentication was Persona/BrowserID... but that will likely require some dev resources unless upstream just happens to have that already.
Priority: P4 → P5
Jake: Deploying this service is dependent on a security review, but there is no clear drivers for this. Since there is no clear goal or associated with it, we won't schedule it at this point, but if someone takes it on to drive it forward, please reset the security review flag to ? and we will look at it then. FYI, there have been holes in status.net in the past, and the status.net guys were super responsive, but we didn't actually run a review of the platform when the bugs were reported.
Flags: sec-review? → sec-review-
I have written some bespoke plugins in the past for status.net so I could provide some developer resources to write a Browser ID plugin and can also help with setting up the Twitter bridge, .. on our server(s) I would like to see Mozilla moving away from using closed web services like Basecamp, Yammer, .. when there are open source alternatives. Enough said. It would be great to build our own community site along the lines of spreadfirefox.com but for the whole Mozilla community but I have now gone off topic :) Thanks for stepping up and looking into this. Let me know if I can help. Best, Paul
There's a couple separate projects already underway that appear to fulfill a similar need and seem to have more traction... I'm going to WONTFIX this bug in favor of those. The ones I know of are BuddyCloud (bug 781964) and what appears to be something we're developing from the ground up... http://benjamin.smedbergs.us/weekly-updates.fcgi/. If either of these sounds unlikely to be useful, feel free to re-open and we can look into this in more detail.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.