Hi Cyrille, > As promised, here's a proposal (in attachment) for redesigning > the Perl group's team and home pages. > > The goal for the moment is to show how these 2 pages could be > re-designed to better differenciate their respective purposes > (ie: the homepage is for reference, more static, information, > while the team page is more for work documents). So, please try > to focus on this objective at the moment (though all comments > are welcome anyway). Good job! First, let me say thay I like the way you've structured the homepage contents. With these changes it will become pretty clear that the wiki is a working area. Maybe I'd enhance the text linking to the homepage a little so people know what kind of references they can find there (goals, contact, policies, howtos, talks, etc). > 1) Should we still reference PET? (Is PET ever going to be used > again? Many of the PET information and features have been integrades into tracker.debian.org, e.g. https://tracker.debian.org/teams/pkg-perl/ > => update https://perl-team.pages.debian.net/changelog.html > accordingly I'm not sure that those PET keywords are also supported in tracker.d.o. If they're not, we can either try to add support for them or forget about them altogether and get rid of this page. > 2) Is this still used?: https://perl-team.pages.debian.net/qa/ I think those files haven't been updated since we moved our repos to salsa.d.o. Tracking those issues is still an interesting thing to do IMHO, though we may need to find a different place for that. > 3) I would like to move the welcome pages to the team's website > rather than keeping them in the wiki. What do you think? Makes sense, since welcome pages aren't going to change a lot. > 4) What's the purpose of this link: "Debian Perl Group on > Launchpad (also has a mailing list for bugs in Ubuntu)" To keep track of bugs reported in Ubuntu thay may be interesting to deal with in Debian too (e.g. if there's something wrong with our packaging). > 5) What's the purpose of linking to > https://packages.debian.org/sid/dh-make-perl on the team page? > wouldn't it be better to link to a man-like page (as done for > other pages like forward.html or git.html)? Linking to dh-make-perl manpage would be better, indeed. > 6) What's the purpose of pkg-perl-tools (it seems to hold > important information)? (ah ok, I found the info in its control > file => wouldnt' it be good to create a README.md file at the > root of this repo?) What about linking to dpt manpage instead? Thus, we won't need to duplicate the same information in the README. > TODO > > 1) Keep documents in sync with what can be found in other repo > (eg: pkg-perl-tools). That's one of my main concerns regarding the homepage contents. I've been looking for some way to extract POD contents from differents tools and modules that we could then insert in our homepage, and then I found podselect which looks promising. > I guess it would require and update to the update-website > script in the perl-team.pages.debian.net package. I've been playing around moving all related website scripts from the scripts repo to perl-team.pages.debian.net repo. The easiest way would be cop/remove the scripts and let their history on the former repo, but I'd like to move them with their whole log and commit history instead. Unfortunately, the last time I was working on that in December I couldn't decide how to proceed and no change was actually performed. Do you want me to go on with this before adding more features to those scripts? Cheers! Alex -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Alex Muntada <alexm@debian.org> ⢿⡄⠘⠷⠚⠋ Debian Developer - log.alexm.org ⠈⠳⣄⠀⠀⠀⠀
Attachment:
signature.asc
Description: PGP signature