Those are all solid products for billing. Tough none of them are both open-source and have the scalability of streaming aggregation. Even Lago is AGPL which can be challenging for some.
#Received: from elbmasnwh002.us-ct-eb01.gdeb.com ([153.11.13.41]
# helo=ebsmtp.gdeb.com) by mx1.gd-ms.com with esmtp (Exim 4.76) (envelope-from
# <bmandes@gdeb.com>) id 1VS55c-0004qL-0F for support@erratasec.com; Fri, 04
# Oct 2013 09:06:40 -0400
#To: <support@erratasec.com>
#CC: <ebsoc@gdeb.com>
#Subject: Scanning and Probing our network
#From: Robert Mandes <bmandes@gdeb.com>
#Date: Fri, 4 Oct 2013 09:06:36 -0400
#
#Stop scanning and probing our network, 153.11.0.0/16. We are a defense
#contractor and report to Federal law enforcement authorities when scans
#and probes are directed at our network. I assume you don't want to be
#part of that report. Please permanently remove our network range from
#your current and future research.
#
#Thank you
#
#Robert Mandes
#Information Security Officer
#General Dynamics
#Electric Boat
#
#C 860-625-0605
#P 860-433-1553
You would hope a defense contractor was smarter than this but of course they tend not to be... threatening to put a maintainer in a report to Federal law enforcement is weak sauce.
I'm hiring a Software Developer Apprentice, full-time and paid.
There will be an emphasis on learning and quality, not speed of development. You'll work on: frontend and backend web applications, mobile applications, desktop applications, and APIs.
=============================
Software Developer Apprentice
This is an excellent opportunity for an aspiring software developer who is eager to learn by doing.
Details:
The position is full-time and paid. Day to day work will be remote, but candidates may prefer to relocate to New York City temporarily for in person mentorship and learning opportunities.
In this position you will be tasked with a variety of software development projects spanning the entire stack using the following technologies:
* Web frontend: React
* Web backend: Ruby on Rails
* Mobile: iOS with Swift
* Desktop: Cross platform with Electron
* Platform: REST and GraphQL APIs
You will work on real projects and receive mentorship on software development and industry best practices. There will be a strong emphasis on producing quality work and becoming a great developer and less of an emphasis on speed of development.
This is not a typical job at a company. It's a paid full time apprenticeship opportunity working with John Britton in an individual capacity.
Qualifications:
This is an apprenticeship: zero professional experience is required. Candidates must, however, have demonstrated determination and an unwavering desire to learn. Acceptable evidence may include: completed coursework, self study records, side projects, and personal recommendations.
thanks for reaching out. The individual case was resolved (found a local copy). But I find the policy worrisome for future projects. If the customer support was happy to reenable access for me, what is the point of the current policy?
That's why I've been migrating my Github/lab projects to IPFS as well. I have a few cheap VPSes I have my stuff pinned.
"Cloud" (read: someone else's server) is unreliable at best, or malicious at worst like this case. The people may not be bad actors, but the tech definitely is.
If people can get the fork back after reaching out to support@github.com, why would not GitHub resolve this issue once and for all, so that people will not need to reach out to support@github.com any more?
If Support just do this kind of thing why not put it in the UI. It's like unlinking a fork - GitHub Support just do it on asking - but why is GitHub spending unnecessary manpower when it could just be a button in the settings saying 'Unlink'.
As a teacher you can get as many private repositories as you need for your course for free. Just make a request here: https://education.github.com/discount
This is a highly discouraged solution, multiple accounts lead to trouble with students and their local git configurations. They have to be knowledgeable enough to keep things separate.
1. We're working with the OAuth permission model that exists today, but I've passed along your feedback to our platform team. The generic use case for Classroom for GitHub is to create a new organization to use for student assignments and use Classroom for GitHub to manage that organization. If / when you decide to stop using Classroom for GitHub you can remove your organization and it will clean up after itself.
3. I'm having a hard time understanding your situation, but would appreciate it if you could file an issue at https://github.com/education/classroom/issues/new, can't promise that it will be fixed immediately, but need to gather feedback like this.
Thanks for the response! Related to (1), the issue was more that when a _student_ visits an assignment page, they get the same big permission list as an instructor; it makes sense that instructors might need a plethora of permissions. Is that necessary for students?
A couple of things I've found, using GitHub for individual assignments (I also use it in another unit for a class-wide project, where it works very well)
- user management is a bit of a pain. Students are always late getting their github usernames to me, often with typos, and there are three different dates during term when the class-list changes (last day to enrol, last day to withdraw without incurring a HECS fee, last day to withdraw without academic penalty). If you could do an LTI endpoint, that would be helpful, as most LMSs support LTI. At the moment, we're considering running GitLab instead, as that supposedly has LDAP and so can use our university server logins.
- using teachers-pet (GitHub's command-line tools) for assignments this term, I found an issue where a student made a public fork of their assignment repository. Unfortunately this is problematic, as it could cause students to (accidentally) run into trouble with university plagiarism policies (where putting your work up for others to plagiarise in an assignment is also outlawed).
Those are two very common issues that we've tried to address with Classroom for GitHub.
You no longer need to collect usernames, just distribute an invitation URL and have your students include their student number or name in the repository description or README.md.
Forking is intended as a collaboration tool, so it makes sense that every member of the network can see all forks in the network. In a classroom setting, however, this might not make sense. Classroom for GitHub doesn't utilize forking, instead it creates independent repositories and pushes the starter code without using forks.
This needs some videos to show what it can do. Not many teachers know what GitHub is and if I wanted to suggest this as a possible option I could not explain it to them.
Maybe a video showing the creation of an assignment and sending it out (url via email, is it?), students completing the assignment, and teachers looking over a completed assignment.
If that is a poor example of what this does then I missed the point entirely.
* Lago - https://www.getlago.com
* Octane - https://www.getoctane.io
* Metronome - https://metronome.com