Gentoo Archives: gentoo-project

From: Seemant Kulleen <seemantk@×××××.com>
To: gentoo-project@l.g.o
Cc: Gentoo Dev <gentoo-dev@l.g.o>
Subject: Re: [gentoo-project] Rekindling Gentoo News
Date: Sun, 15 Jan 2017 09:11:30
Message-Id: CAJEWDoU0-gJi1o5pfoX7+Yg_2h=bf3+K1aMzsX846Qo_am1hLw@mail.gmail.com
In Reply to: [gentoo-project] Rekindling Gentoo News by Matthew Marchese
1 Happy 2017 to you Mr. Marchese,
2
3 You've brought wonderful news!
4
5 If there's interest in data visualization (with d3.js), I'd love to chat
6 about how I might help.
7
8 Cheers,
9 Seemant
10
11
12
13 *--*
14 *Oakland Finish Up Weekend*
15 Be Amazed. Be Amazing.
16 Get Mentored | Get Inspired | *Finish* *Up*
17 http://oaklandfinishup.com
18
19
20 On Sat, Jan 14, 2017 at 11:41 PM, Matthew Marchese <maffblaster@g.o>
21 wrote:
22
23 > Hi all,
24 >
25 > Huzza! Welcome to 2017! This year I would like re-ignite the Gentoo news
26 > project. It has been smoldering for some time and I think with a small
27 > bit of interaction from YOU (the developers, the council members, and,
28 > yes, even YOU foundation members), it would be easily rekindled.
29 >
30 > To be clear, I have no absolutely no intention of writing a full
31 > newsletter each month. Most people's attention spans are not long enough
32 > to even read though a newsletter or make it this far into an email, so
33 > I'm not looking to spend a lot of time doing that. I have something much
34 > simpler in mind. Presently the GMN project has moved. It is now called
35 > simply "News". We have a #gentoo-news channel on Freenode and a
36 > news@g.o mail alias.
37 >
38 > Here is the YOU part: the only way this project will work is if YOU push
39 > news announcements to ME. As you understand, Gentoo is a broad ecosystem
40 > with LOTS going on _constantly_. I only use one desktop environment and
41 > can't look at #gentoo-commits / gentoo.git log to track the changes of
42 > major successes or new additions to the main repo.
43 >
44 > You can use either the IRC channel or news@g.o to push news items
45 > of interest to me. I will handle weeding them out and getting them to
46 > the developers and the community on the social sites. The IRC channel is
47 > preferred because I am always connected, and messages are instant; but
48 > again, as it should be in Gentoo, _your choice_.
49 >
50 > Example news items could be:
51 >
52 > * New release of Gnome (or any other supported DE).
53 >
54 > * New, interesting packages added to the main repo.
55 >
56 > * New projects - Tell me about the project goal and what you're working
57 > on. I will also watch the gentoo-project list, but LOTS of times it's
58 > easy to miss things.
59 >
60 > * Project changes - Want the community to test something? Want to warn
61 > us about something? Want to remind us of something? Want to scold
62 > inactive members of your project? You can now do that on social sites so
63 > that the world can see! Hope you caught the sarcasm in that last sentence.
64 >
65 > * Event annoucements - Tell me where you're meeting and what you'll
66 > talking about. Give me the highlights of a past the event. Tell me why
67 > attendees should go to your event. Share pictures from your event.
68 > Gentoo is going to be present as FOSDEM 2017. What about Scale? I'd be
69 > happy to push invitations to the social sites. Just tell me what to say.
70 > For event invitations should also have an announcement on the front page
71 > of the main site, IMO, but we can start with getting them to our social
72 > sites.
73 >
74 > * Anything that is exciting that has happened for Gentoo - This goes for
75 > projects that completed a long or short term goal, Gentoo being
76 > recognized for something important, or Gentoo is seen somewhere in the
77 > news media. Good OR bad external news can be shared. You can even rip
78 > something off the forums or Reddit and re-share it in #-news.
79 >
80 > * Gentoo ported to run on a strange or unusual piece of hardware -
81 > Recently I saw Gentoo being ported to the PS4. That was something that
82 > should be shared with #-news.
83 >
84 > Once it gets to me, the news will probably go out one news item at a
85 > time, in one or maybe two sentences. This way we can be reporting news
86 > as it develops, instead of releasing news in a monthly --oneshot like
87 > the old project. As mentioned for event invitations above, larger or
88 > more important news items can hopefully be shared on the main www page.
89 >
90 > Also, the QA project seems to be good at generating all kinds of graphs
91 > and charts, so I have no plans to use the old Python scripts for those
92 > kinds of things. I do have some other ideas up my sleeve for this
93 > project in the future.
94 >
95 > The one thing to take away from this email: if you have some news item
96 > that has some value to the community you should share it in #-news. It
97 > would be great to release early and release often in terms of news. This
98 > will not happen without YOUR help.
99 >
100 > Anyone who wants to aid these efforts welcome to join the project.
101 > Looking forward to hearing any thoughts from you on things that may need
102 > to be flushed out a little.
103 >
104 > Your docs doctor and news host,
105 >
106 > Mr. Marchese
107 >
108 >
109 >
110 >
111 >