Difference between revisions of "EPSCI Group Meeting Jul. 6, 2020"
| Line 41: | Line 41: | ||
#* JLab Common Environment (CE) + SPACK | #* JLab Common Environment (CE) + SPACK | ||
#* SRO Activities (Vardan G.) | #* SRO Activities (Vardan G.) | ||
| − | #** No SRO Meeting this afternoon! | + | #** EIC ERO meeting today at 11am ([https://bluejeans.com/577523487 bluejeans]) |
| + | #** No EPSCI SRO Meeting this afternoon! | ||
# Publications | # Publications | ||
#* [[Fortnight Papers]] | #* [[Fortnight Papers]] | ||
Revision as of 12:12, 6 July 2020
The meeting time is 10:00am.
Connection Info:
You can connect using BlueJeans Video conferencing (ID: 253 300 597). (Click "Expand" to the right for details -->):
Meeting URL https://bluejeans.com/253300597?src=join_info Meeting ID 253 300 597 Want to dial in from a phone? Dial one of the following numbers: +1.888.240.2560 (US Toll Free) (see all numbers - https://www.bluejeans.com/premium-numbers) Enter the meeting ID and passcode followed by # Connecting from a room system? Dial: bjn.vc or 199.48.152.152 and enter your meeting ID & passcode
Agenda:
- Previous meeting
- Announcements
- Beam delivery for physics starts July 27th(ish)
- Github Private Repositories (see below)
- NERSC Activity support
- Ongoing Activities
- Hall A/C Software support (Carl T.)
- EVIO-6 (Carl T.)
- JANA2 (Nathan B.)
- JLab Common Environment (CE) + SPACK
- SRO Activities (Vardan G.)
- EIC ERO meeting today at 11am (bluejeans)
- No EPSCI SRO Meeting this afternoon!
- Publications
- AOT
GitHub Private Repositories
Dear JLab GitHub users,
JLab's licensing arrangement with GitHub presently allows a maximum of 450 'private' repos to be created under the JeffersonLab organization. We recently filled that quota and are presently unable to create new private repos. Unfortunately, due to a major restructuring of GitHub's licensing plans there is no easy way to simply increase that limit right now.
We are asking all GitHub members in the JeffersonLab organization to review their repos marked 'private' and do one of the following to help address this issue in the near term. This link shows all private repos:
https://github.com/JeffersonLab?q=&type=private
1) If the repo doesn't really need to be 'private', change
its Visibility to 'public' in the repo settings.
* NOTE: 'public' does not mean that others can modify
the repo. If you would be comfortable putting
a tarball on a wiki or webpage somewhere (ie.
public_html/, etc), then 'public' should be
fine on GitHub.
2) If the repo is unused and unneeded, then delete it. (Check with collaborators first!)
3) If appropriate, it could be transferred to your personal
account. (Se repo settings: 'Transfer Ownership' at
bottom.)
** One positive change in GitHub's setup is that
personal accounts can now create private repositories.
That used to be a paid-only feature. So, some classes
of work (ie. papers, proposals, etc) can be well served
under 'free' personal accounts.
- Larger projects, and JLab-specific work should remain
attached to the JeffersonLab organization.
- NOTE: There is no limit on 'public' repositories. Don't worry about those at all.
We're working on a long term solution to this issue, but please investigate the steps above to help us all out in the near term. _______________________________________________ Jlab-scicomp-briefs mailing list Jlab-scicomp-briefs@jlab.org https://mailman.jlab.org/mailman/listinfo/jlab-scicomp-briefs
Minutes:
TBD