I just fired off the email requesting bio updates. https://lists.apache.org/thread.html/69d8573d6372a319e0cf47326aefa64e6c7c61af450c79738d0926d5@%3Cdev.tinkerpop.apache.org%3E
After that's settled, I think we're done with this issue and we can just maintain the process going forward. On Fri, Jan 25, 2019 at 8:00 AM Stephen Mallette <[email protected]> wrote: > All of the modal panels are now present in the downloads.html file. I made > a best effort at specifying the "Release Manager" for each version. If you > did a release in the past you might want to take a look at what I have > there to make sure it's all accurate. Feel free to just correct it as > needed. > > > https://github.com/apache/tinkerpop/commit/991c19ee6a1d6b21fb4d1661af04797947dee391 > > afaik, only Ted Wilmes, Jason Plurad, Robert Dale and myself have ever > done releases, so this email is mostly for them. Apologies if I missed > someone or got something mixed up. Obviously, it will be easier to keep > track of this going forward. > > On Mon, Jan 14, 2019 at 9:19 AM Stephen Mallette <[email protected]> > wrote: > >> I just pushed the rework of the model for "Release Notes" and >> contributions - as I mentioned during the 3.4.0/3.3.5/3.2.11 release >> process what I'd thought would work didn't work out so well in practice. >> I've instead come up with this form: >> >> >> https://github.com/apache/tinkerpop/commit/b968099ae17e1104469fa0a18425aecfcb7b2d09 >> >> which replaces the "javadocs" link on the download/release page with a >> "contributors" link which pops up a modal containing the "git shortlog" >> (and whatever else we'd like to see in there). I only did it for the most >> recent release at this point (and have not yet published). You can >> generate-home.sh to view it. Kuppitz is going to try to automate generation >> of the previous release modals. Once that's done, we can publish the site >> with that change. >> >> On Wed, Dec 19, 2018 at 11:20 AM Stephen Mallette <[email protected]> >> wrote: >> >>> Some time has passed since this thread was last touched, but I got >>> around to documenting the things discussed here: >>> >>> >>> https://github.com/apache/tinkerpop/commit/4b10cfda1f85aefe3017ec7fc25791d409719329 >>> (Release Notes) >>> >>> https://github.com/apache/tinkerpop/commit/0f82111ecd1a1c966760c9009d486eae4adc8a3e >>> (Contributor List) >>> >>> Note that I didn't deal with "Friends of TinkerPop" stuff. I'm still not >>> sure what that should be and it probably needs more discussion. Anyway, >>> please let me know if there are any concerns or things forgotten...if not >>> we will proceed with this direction with/after 3.4.0 >>> >>> On Mon, Oct 8, 2018 at 2:33 PM Stephen Mallette <[email protected]> >>> wrote: >>> >>>> I'm going to assume lazy consensus on the general points of this >>>> proposal as its been a few days now since I originally posted it. I will >>>> try to document the general aspects of what was presented here in the dev >>>> docs and will post back here when I've done so. I think we can take this >>>> discussion in two separate directions at this point one for the release >>>> notes changes and one for the web site (probably new email threads i >>>> guess). I don't think we need to try to force any of this in for the >>>> current release that we're dealing with. In fact I'll probably make the dev >>>> doc changes in a branch so that they don't go in as part of this release. >>>> >>>> On Wed, Oct 3, 2018 at 11:59 AM Stephen Mallette <[email protected]> >>>> wrote: >>>> >>>>> There has been some discussion within the PMC over the last month or >>>>> so about how to recognize the various contributors to Apache TinkerPop. We >>>>> currently have this: >>>>> >>>>> http://tinkerpop.apache.org/#committers >>>>> >>>>> but we think some changes should occur. First, we would like to better >>>>> recognize the list of folks who contributed during a particular release >>>>> period to include: >>>>> >>>>> 1. git contributions for a release will be aggregated and presented in >>>>> the release notes. >>>>> 2. non-code contributions to a release will be added and presented in >>>>> the release notes. >>>>> >>>>> I don't know if "release notes" means CHANGELOG or Upgrade Docs or >>>>> something else - I suppose that remains up for discussion. The issue is >>>>> more about capturing these contributions better on a per-release basis. >>>>> >>>>> Second, we expect to modify the website in that space given in the >>>>> link above - rather than have it read "Apache TinkerPop Committers" it >>>>> will >>>>> instead be "Apache TinkerPop Contributors" and it will include both >>>>> official committers as well as "Friends of the TinkerPop" (working >>>>> title...suggest something better??). >>>>> >>>>> For the committers section, individuals can keep this information up >>>>> to date themselves (because they have access to the git repository), but >>>>> we >>>>> will ask for a bio update from each person every 6 months via email with a >>>>> request to indicate an "active" or "inactive" status. If you are >>>>> "inactive" >>>>> it simply means that you aren't currently participating in the project. >>>>> Irrespective of being active or inactive, your name and tenure >>>>> accomplishments remain present on the front page of the web site. Being >>>>> "inactive" does not affect your status as an Apache committer/PMC member - >>>>> that remains unchanged. Should you decide that you are inactive at some >>>>> point, note that there is no special process to become "active" again - >>>>> you >>>>> just have to update your bio to do so. The format of the committer section >>>>> would be basically the same as it is now but would have active and >>>>> inactive >>>>> sections, sorted by date of TinkerPop commitership (or membership in the >>>>> pre-Apache days), as they are now. >>>>> >>>>> The new "Friends of the TinkerPop" section will be a listing of those >>>>> people who have promoted the project in some positive capacity (e.g. >>>>> developed a third-party library that has some good benefit to the >>>>> community) but aren't committers/pmc members. >>>>> >>>>> There's still a fair bit to sort out in terms of how this will be >>>>> implemented, but these are the general big picture items. Please let us >>>>> know what you think and then we can drive into details. >>>>> >>>>> >>>>> >>>>> >>>>> . >>>>> >>>>
