Hey Jason,
First of all, I did not read the new website thoroughly; I only ran over it searching for problems, while trying to click in as many links as possible. Also, please note that my intention is not to bash it, but just to report the issues I have found. In any case, even if these issues are not fixed right now, I see no blocking factor for the website to be switched over. Here is the (non-exhaustive, but exhausting) list of issues found: In contributing (http://new.gem5.org/contributing), "The full style guideis outlined here: " is missing the link. References to (http://new.gem5.org/contributing/changes/) should be turned into references to (http://new.gem5.org/contributing/). "Module owners" (as in http://new.gem5.org/governance/Module_owners) feels like a poor word choice for the "community led" idea. IMHO another "title" should be used, such as "Module Coordinators". gem5 101 has the uttermost need to be revisited, and until then there should exist an obsoleteness warning for the user. For example, the cache assignment (http://pages.cs.wisc.edu/~david/courses/cs752/Fall2015/wiki/index.php?n=Main.Homework5) is outdated due to the RP changes. In http://new.gem5.org/documentation/, the link to the Doxygen documentation is not clickable. The page about reporting problems (http://new.gem5.org/documentation/reporting_problems/) feels too hidden for its importance. Maybe it should belong in the list of main pages, along with Contributing, Events, etc. Now the replacement policies are used everywhere, but it is only listed in the Memory System drop list. It should have a symbolic link in the Ruby Memory System drop list too (although it would mess with the Next/Previous buttons). The page for Indexing Policies has the wrong header title (it is "Replacement Policy" as of writing this). In the coherence page (http://new.gem5.org/documentation/general_docs/memory_system/classic-coherence-protocol/) there are references to M5 2.0 and others. Is it even still relevant to keep this info? I think a link should be added in the Debugging drop list to the Reporting Problems page. Page (http://new.gem5.org/documentation/general_docs/cpu_models/O3CPU) has a ThreadContext link, which points to the old website's page. It should be pointing to Execution Basics (http://new.gem5.org/documentation/general_docs/cpu_models/execution_basics) instead. The page names are inconsistent. I have found many variants, as: new.gem5.org/page_example, new.gem5.org/page-example, and new.gem5.org/PageExample. Dead links: http://new.gem5.org/governance/Roadmap http://new.gem5.org/documentation/general_docs/architecture_support/arm_implementation/ http://new.gem5.org/governance/Module_owners Regards, Daniel Em terça-feira, 7 de janeiro de 2020 18:11:19 GMT+1, Jason Lowe-Power <[email protected]> escreveu: Hi dev-list, Does anyone see any blocking issues before switching to the new website as gem5.org? The only thing left on my "to do" list is to make a deep copy of the old website to archive and make publicly available ( https://gem5.atlassian.net/browse/GEM5-230). If not, we'll plan on switching over next week. Thanks, Jason On Tue, Dec 17, 2019 at 5:15 PM Jason Lowe-Power <[email protected]> wrote: > Hi all, > > I'm excited to announce that we have a beta version of a re-designed > website at new.gem5.org! The old wiki has needed a refresh for a few > years, and we’re excited to finally have something to share with the > community! We hope the new site has better usability and makes it easier to > find information about gem5 and how to use it. If you have any questions or > comments, don’t hesitate to reach out by replying to this email. > > We will leave this website at new.gem5.org for the next few weeks. Please > let us know if there’s any blocking issues before we turn off the old wiki > pages. Before fully transitioning, we will download a static copy of the > entire old website (including the old code reviews) and move this to > old.gem5.org for archival purposes (and in case we missed anything!). > > I'd like to thank all of those that have contributed so far. Specifically: > Jingwen Low who designed the site > Ali Saidi who kicked this off by converting the wiki to markdown almost > two years ago > Bobby Bruce who has put it a ton of time moving documentation > And Jared Barosci, Hoa Nguyen, Krithiga Murugavel, Ayaz Akram, Trivikram > Reddy, Marjan Fariborz, Mahyar Samani, Julian Toya Angeles, and Muhammet > Soytürk who have helped move documentation from the old wiki to the new > site. > See https://github.com/gem5/new-website/graphs/contributors for details > > Details on the current status of the migration can be found on Jira ( > https://gem5.atlassian.net/browse/GEM5-110). We also have a specific > issue for migrating the old documentation to the new site ( > https://gem5.atlassian.net/browse/GEM5-115). We’ve already moved most of > the documentation, but there are still a few pages that we could use your > help with! > > There will be some rough edges as we transition. Some links may be broken, > and it’s possible we missed pages that should be migrated. If you find any > issues, please let us know via the mailing list or by opening an issue on > Jira. > > The website is currently hosted on GitHub pages. If you’d like to > contribute, feel free to create a pull request on the source repository ( > https://github.com/gem5/new-website). > > Cheers, > Jason > _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
