search

SSAGESproject / ssagesproject.github.io

Website for SSAGES project
https://ssagesproject.github.io
2 stars 4 forks source link

Requested Updates #5

Closed cbezik closed 7 years ago

cbezik commented 7 years ago

A list of various things people (primarily Juan and/or @jonathankwhitmer) have asked of the site:

Some of these are clearly easier to pick off than others and I'll tackle them shortly. I think the open-ended things that I can't tackle yet are:

  1. Resolving the tracking of downloads/user count is probably the most open area of discussion. I'm in favor of setting up a mailing list and user forum to count our numbers (in addition to centralizing the count, this also more accurately estimates dedicated users - even if we could easily track direct downloads, do we really want to count someone who downloads the code and never uses it?).
  2. Given the desire to feature COPSS/SSAGES side by side we should probably decide on the ultimate title and URL for this site. I'll use placeholders in the meantime.
jonathankwhitmer commented 7 years ago

I think imecodes is a better title, given the intent to feature both it and SSAGES equally.

Download tracking is something we need to work on. We can track it for .tgz downloads, and for developer forks, but that isn't how must people will use a github source repository.

Jon

On Fri, Apr 28, 2017 at 5:47 PM, Cody Bezik notifications@github.com wrote:

A list of various things people (primarily Juan and/or John) have asked of the site:

  • Redesign to feature SSAGES and COPSS equally.
  • Move the site to a better URL (in short term, something like https://miccom.github.io/SSAGES/ https://miccom.github.io/SSAGES/ (or, pursuant to the above, https://miccom.github.io/imecodes ?). Longer term I'm told we have our own server now and can probably redirect to an arbitrary URL.
  • Track downloads. This is a very difficult feature to implement as long as we distribute the code via GitHub, since it cannot track clones of the repository for SSAGES. I do not personally believe we will ever be able to provide one centralized download counter. It is probably better to track users via signups to a mailing list/forum.
  • Provide semi-private access to a tarball of the development branch of SSAGES. The idea described to me was gating the download by requiring an email address. In the site's current form this could only be accomplished with a third-party service and would probably provide a link to some shared Dropbox folder (or something along those lines).
  • Reorganize contributors to most prominently feature Whitmer/de Pablo group contributors ("core developers") and place other credits below.
  • Clearly attribute whether someone contributed to SSAGES/COPSS/both.
  • Add "papers" page to house links to publications using SSAGES/COPSS/both.
  • Include Ben's video of ADP isomerization.

Some of these are clearly easier to pick off than others and I'll tackle them shortly. I think the open-ended things that I can't tackle yet are:

  1. Resolving the tracking of downloads/user count is probably the most open area of discussion. I'm in favor of setting up a mailing list and user forum to count our numbers (in addition to centralizing the count, this also more accurately estimates dedicated users - even if we could easily track direct downloads, do we really want to count someone who downloads the code and never uses it?).
  2. Given the desire to feature COPSS/SSAGES side by side we should probably decide on the ultimate title and URL for this site. I'll use placeholders in the meantime.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/WhitmerGroup/SSAGES-site/issues/5, or mute the thread https://github.com/notifications/unsubscribe-auth/AJ5QTvPYXHZ46RDQntcZO7OsyGk99vmbks5r0l5ggaJpZM4NMAYQ .

-- Jonathan K. Whitmer \ Chemical and Biomolecular Engineering Assistant Professor \ University of Notre Dame jwhitme1@nd.edu \ 122A Cushing Hall ph: (574) 631-1417 \ Notre Dame, IN 46556

cbezik commented 7 years ago

See pull request #6 for partial addressing of this issue. What I have so far is my proposal for restructuring; as usual, none of the content is final and still needs updating. Let me know what you think so far.

jonathankwhitmer commented 7 years ago

Cody-

This looks very good. I would like to add a couple of 'under construction' items to the site [for now, they should just have placeholders, since we don't have the content for them yet].

1) There should be a 'validation' site in the menu that will eventually contain information on how these codes have met their MICCoM validation targets. 2) There should be a 'tutorials' or 'school' section where we can put extra information on the test cases provided with the codes and slides/examples from the MICCoM school.

Best, Jon

On Fri, May 12, 2017 at 5:27 PM, Cody Bezik notifications@github.com wrote:

See pull request #6 https://github.com/WhitmerGroup/SSAGES-site/pull/6 for partial addressing of this issue. What I have so far is my proposal for restructuring; as usual, none of the content is final and still needs updating. Let me know what you think so far.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/WhitmerGroup/SSAGES-site/issues/5#issuecomment-301190164, or mute the thread https://github.com/notifications/unsubscribe-auth/AJ5QThBVRrt6FGeOf9z9Y5OdZcufsAO0ks5r5M7DgaJpZM4NMAYQ .

-- Jonathan K. Whitmer \ Chemical and Biomolecular Engineering Assistant Professor \ University of Notre Dame jwhitme1@nd.edu \ 122A Cushing Hall ph: (574) 631-1417 \ Notre Dame, IN 46556

cbezik commented 7 years ago

The site URL issue is fixed; @jonathankwhitmer, I've added these under construction pages to the website in the next pull request. I am going to pull out the issues related to user tracking and put them in a separate issue, then close this issue after the next pull request.

cbezik commented 7 years ago

I think everything in here has either been addressed or made a separate issue.