cnerg / cnerg.github.com Goto Github PK

The current instructions offer a path that uses a docker image to build the website. To avoid polluting the docker-mounted filespace with files owned by root, the docker image is started with the UID of the current user.

The first step in a few (related) targets is to run git fetch once the docker image is launched, but the UID of the current user doesn't exist in the docker image, so git throws an error.

Unless we can fix this inside the docker image (probably hard in general) we probably need to ensure that fetch happens prior to launching the docker image.

Links for skills development are missing (community/manual/skills), here are some suggestions for what to include in each category (others add ideas too if we want to include more than one link per category):

Compiling and Linking Code:

• https://www.learn-cpp.org/
• https://cmake.org/cmake/help/latest/guide/tutorial/index.html

Unix Command Line:

• http://swcarpentry.github.io/shell-novice/

Literature Review:

• ??

Version Control (not a category but maybe add?):

• http://swcarpentry.github.io/git-novice/

recommend some refreshments that will help you be productive

GanttDue: 2019-01-05

Sign up to provide refreshments of your choice. (See #125 to make requests)

GanttDue: 2019-01-05

Everyone needs to spend a little time thinking of eye candy that they can generate to show off the capabilities we have developed

GanttDue: 2021-01-01

Consider a more fine-grained separation of content, specifically the philosophical from the practical and policy

GanttDuration: 30

• secure a room on campus as a default/backup
• identify other interesting venues that may be off-campus

Important features:

• we can bring our own food/drink
• strong internet
• plenty of power
• accessible by bus/bike

GanttDue: 2019-01-01

A recent PR (#220) introduced an error in the handling of data of alumni/former members.

This can be repaired by testing whether "Alumni" is contained rather than matches.

Zotero data is now the primary source for all publication lists on the website. Each person should review their "own" entries in Zotero to ensure that the metadata is complete, specifically:

• url to publication (if available)
• abstract text
• author lists

Review how metadata is used by plugin and develop guidance for which metadata is important and how to populate it

• record type
• DOI or URL
• date
• etc

GanttDuration: 45

@gonuke just added ORCID as a "service" option for personal bios (in #209). It may be a good idea to add everyone's ORCID who has one (mostly thinking of grad students).

TODO?

• @gonuke
• @MicahGale
• @lewisgross1296
• @nuclearkatie
• @biegelk
• @ngranda
• @stompsjo
• @connoramoreno

My bio has gone quite out of date! I will issue a PR to update to more modern information

A lot of the personnel image sizes are really big.

It isn't terribly noticeable, but I do experience slow loading times once in a while.

GanttDue: 2019-01-10

Review all Zotero records for metadata identified in #95

GanttDependsOn: 95
GanttDuration: 30

This should have a similar separation of page source and built HTML pages. Because these auto web pages require the HTML in the master branch, it will need to be a little different, with source in a different branch and a build process that runs Sphinx in the master branch.

The copyright statement is currently through 2021. 2023 can definitely be added. It’s unclear if 2022 can be added as well though.

The first publication page should list only a selection of publications (most recent? most important?), but offer another page with a complete list

GanttDuration: 45

Use Zotero API to formulate an HTTP POST query for bibtex data

GanttDependsOn: 95
GanttDuration: 45

Metadata for items in the thesis archive sub-collection on Zotero is inconsistent. This results in poor rendering on the website. Using the website rendering as a guide, systematically improve the metadata across the set of all documents.

Create a robust philosophy section based on the expectations document and community ideals

GanttDependsOn: #119
GanttDuration: 60

... and help him stage said picture :)

might be expected tho....

community/events page gives a 404 error. If there are no events, have a default "no events are scheduled." Also what kinds of events are you envisioning here?

This is following a discussion we had with @kkiesling .
I am not sure how to phrase it exactly.

I believe that being part of the community and then following the code of conduct, shall also mean that it is expected that you will report transgression of the code of conduct you witnessed
There is probably cases where that can be more complicated...

need descriptions for the rest of the roles on community/manual/tasks_roles:

• license manager
• hardware manager
• software installation
• publication list maintenance
• access control
• project reporting

Description

The events page on the Computational Nuclear Engineering Research Group (CNERG) website is currently under development. It could benefit from enhancements to improve its functionality and user experience. This issue proposes implementing the FullCalendar plugin to display events effectively.

I would like to express my sincere gratitude to the entire team for your invaluable contribution to the open-source community by making the CNERG website available as an open-source project. The resources and source code provided on your website have been immensely helpful in the development of NukeHub, and I cannot thank you enough for this.

Proposed Changes

• Integrate the FullCalendar plugin into the events page.
• Utilize a YAML file to store event data for easy management and retrieval.
• Implement functionality to read event data from the YAML file and display it on the events page.
• Enhance the user interface to ensure intuitive navigation and interaction with event information.
• Ensure compatibility and responsiveness across different devices and screen sizes.

Expected Outcome

• Users will have access to a visually appealing and interactive events page.
• Event information will be displayed in a clear and organized manner, improving user experience.
• The integration of the FullCalendar plugin will add functionality such as calendar views in list/month/week/day.
• Maintainers can easily manage and update event data through the YAML file.

Additional Information

• The NukeHub events page (https://nukehub.org/events/) serves as a reference for implementing similar features.

Some CNERG members are mandatory reporters under Title IX and cannot maintain confidentiality under all circumstances. This should be made clear in CoC that now says confidentiality will be preserved.

Modify formatting for readability:

• plugin settings?
• plugin modifications
• CCS

GanttDuration: 60

In community -> manual -> policies, there should be a note about CoE's parental leave policy (and link to it if such a link exists) under vacation and personal leave (though it's not actually a vacation so maybe its own header would be good..).

Add topics to the 2019-01-hackathon.md file

GanttDue: 2019-01-05

Everyone should take some ownership of the projects they are working on and generate at least a page in projects/* to describe what they are working on and possibly collect publications & presentations related to that.

GanttDuration: 90

Add yourself to the CNERG website

1. Create a github account, if you don’t already have one.
2. Fork the CNERG website repository. This can be done by clicking the “Fork” button in the top-right corner. Forking means you have your own version of the repository where you can make changes that won’t be reflected in the main repository.
3. Clone your fork. This will download your fork to a directory on your local machine.
   git clone https://github.com/<github_username>/cnerg.github.com
   If you don’t have git on your machine, you can get it with
   sudo apt-get install git
4. Create a new branch where you will make the changes. (It doesn’t have to be called “add_myself”, that’s just an example.)
   git branch add_myself
5. Switch to your new branch.
   git checkout add_myself
   Note that steps 4 and 5 can be completed simultaneously with
   git checkout -b add_myself
   6.Descend into the directory where the source markdown (*.md) files for staff and students are located.
   cd community/people
6. Create a new directory which will contain all data related to you. You can name it how you like, but most are based on initials.
   mkdir <my_initials> (replace <my_initials> with your initials)
7. Go to your new directory
   cd <my_initials>
8. Create a new markdown file, index.md, which will be your personal page. It is probably a good idea to use someone else’s markdown file as a template. Your personal page should contain your name, contact information, research interests and/or projects being worked on, and education.
9. Upload a picture of yourself.
10. Add yourself to the database of people in _data/people.yml. This file currently has different sublists of people based on their role in CNERG. Each entry should include a name, url - this is the directory that you created, e.g. <my_initals>, image - this is the image that will be used on the page of all group members, and role - this is your title and or description of your role in CNERG.
11. Consult README.md to test locally
12. Once you feel it looks correct and the way you want it, add and commit your changes. This will save your changes to your local clone of your fork.
    git add <new_or_modified_files>
git commit -m “Added <my_name>”
13. It is often very useful to use git status, which will give you information like which files have been modified but are not staged for commit, which files have been modified and have been staged for commit (i.e. they have been git added), and whether you have commits in your clone that are not yet reflected in your github fork or vice versa.
    Push your new branch to your github fork.
    git push -u origin add_myself
    If your fork already contains the branch and you are only updating it with new commits, then git push by itself is sufficient.
14. Create a pull request (PR) between the branch on your fork and the main branch in the main repo. This can be done by using a web browser to navigate to your new branch on your fork and clicking “Pull request”. This will allow other users to review the changes you made and make comments, request changes, or approve your changes. Once your PR has been created, you should be able to see it here.
15. Once you and one or more reviewers are satisfied with your changes, someone with write access will merge your branch into the main repo.
16. Once this is done, you’ll be able to find yourself on the staff and students page of the website

Modify the settings of the plugin, or the plugin itself (if necessary) to show pubs in chronological order

GanttDuration: 60