Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decommission wikidot site #4

Closed
obfuscurity opened this issue Jul 28, 2014 · 15 comments
Closed

Decommission wikidot site #4

obfuscurity opened this issue Jul 28, 2014 · 15 comments

Comments

@obfuscurity
Copy link
Member

We need to kill http://graphite.wikidot.com/ with 🔥, sooner rather than later. Unfortunately there are some content gaps in the RTD site (0.9.x, 0.9.12, etc) documentation site that need to be addressed before we can safely decommission the former. Please detail any below that you can find and I'll make sure to crosslink accordingly.

@obfuscurity
Copy link
Member Author

The "Initial Configuration" section has no content.

http://graphite.readthedocs.org/en/0.9.12/install.html#initial-configuration

@obfuscurity
Copy link
Member Author

/cc @graphite-project/committers

@esc
Copy link

esc commented Jul 29, 2014

+:100:

@esc
Copy link

esc commented Jul 29, 2014

Get rid of the old site, it is just confusing for our users.

@obfuscurity
Copy link
Member Author

@esc I totally agree but we need to identify and fill those content gaps first.

@brutasse
Copy link
Member

Pages that don't really have an equivalent in the current docs/ layout:

@obfuscurity
Copy link
Member Author

@brutasse My thoughts on your list...

Good list. If we come to some consensus I'll begin adding issues to knock this stuff out. No need to rush to destroy wikidot until these items have been addressed and the new site is live.

P.S. I suspect PypeD was a StatsD-like aggregator used in Orbitz.

@esc
Copy link

esc commented Jul 30, 2014

You may want to delete/redo the http://graphite.wikidot.com/high-level-diagram

Other than that I am in favour of the aggregations you suggested.

@obfuscurity
Copy link
Member Author

Yeah, the diagram definitely will be replaced by something.

@gwaldo
Copy link
Member

gwaldo commented Aug 6, 2014

How have y'all been reviewing the rst files? I've done a little work on the install/configure section, and want to validate.

@gwaldo
Copy link
Member

gwaldo commented Aug 6, 2014

Made a dent on the Install / configure sections. Nothing pretty (and not yet validated), but attempted to sanely capture what was missing from wikidot into the current docs. PR coming as soon as I review/test.

@obfuscurity
Copy link
Member Author

Oh, and just so we're clear, it's very important that as much of this work as possible is backported to 0.9.x. Otherwise we won't be able to decommission wikidot since the vast majority of our users will be on 0.9.13 and looking at those sad, broken docs.

🍺, 🍰 and 🍦 for all of our docs helpers and maintainers!

@gwaldo
Copy link
Member

gwaldo commented Aug 10, 2014

regarding "The "Initial Configuration" section has no content. http://graphite.readthedocs.org/en/0.9.12/install.html#initial-configuration", I copied in the files within docs/ that had been modified in the past week or so (since I'd started contributing) into the 0.9.x branch. While the latest and 0.9.x versions of the RTD site have updated, the 0.9.12 (and older) versions have not been updated.

Is this expected behavior? Can anyone explain to me how the RTD mechanism works?

@obfuscurity
Copy link
Member Author

That sounds correct. Older versions are built from the project tags. Since we haven't merged any of the fixes in master or 0.9.x into the respective tagged releases, we shouldn't expect to see those fixes in 0.9.12 or older. But they should appear in 0.9.13 once that's tagged and released.

This is as I understand RTD to work. Someone else please correct me if I'm mistaken.

@obfuscurity
Copy link
Member Author

I've enabled a redirect module for the wikidot site in #5. I don't think we need to formally decommission the old wikidot site as long as this 301 redirect is in place. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants