You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As suggested in the IRC meet-up, we're going to start a newsletter containing information about
new blog posts of the #dgplug planets
merged PRs of #dgplug members
random news on tech / linux / privacy that we are interested in
A bi-weekly release cycle has been suggested. To provide a quality letter, I suggest there should be some reserved time for
information gathering
wrapping things up to a readable document (starting one week before release)
have a live meeting on IRC / etherpad to discuss final changes (maybe one or two days before release)
So new topics / news coming in later than one week before release, would be gathered for the next release already.
Does anyone have a different suggestion or doubts/amendments? Or maybe suggestions on when to release the letters? I feel like this should be on either fixed days of the month of a fixed week day (like e.g. every second Friday) in order to guarantee publication on a regular basis.
I will start the issue of the initial release with a summary of the IRC meet-up
The text was updated successfully, but these errors were encountered:
As suggested in the IRC meet-up, we're going to start a newsletter containing information about
A bi-weekly release cycle has been suggested. To provide a quality letter, I suggest there should be some reserved time for
So new topics / news coming in later than one week before release, would be gathered for the next release already.
Does anyone have a different suggestion or doubts/amendments? Or maybe suggestions on when to release the letters? I feel like this should be on either fixed days of the month of a fixed week day (like e.g. every second Friday) in order to guarantee publication on a regular basis.
I will start the issue of the initial release with a summary of the IRC meet-up
The text was updated successfully, but these errors were encountered: