Pfsense-tools missing from repository
-
-
Thanks for clearing some things up here Jim.
You've allayed some of my fears, hopefully those of others.
Steve
I'm responding to you, since I've sworn off responding to abusive a-holes like doktornotor.
While it took too long (my bad), the -tools access has been restored. Those who had sent in a ssh-key have been invited to the early rounds, so we could test the system.
-
@gonzopancho:
the -tools access has been restored.
ORLY?
-
Those who repeatedly post based on unwarranted assumptions will be ignored.
-
Where's the -tools repo? Will you either make it available or stop this deceptive advertising? How old are you? 5 yrs? Extremely mature behaviour.
-
The '-tools' repo is available.
-
Linky??
-
@gonzopancho:
The '-tools' repo is available.
GOTO - now perhaps you should take a break and let someone else handle this fiasco before you totally kill the project.
-
-
@gonzopancho:
explained here
Not really.
-
!(Not really.)
Keep reading, dude.
-
Is the process to request access to pfsense-tools documented somewhere? Once the current trial period is over, will there be any prerequisites to getting access, or will it be more or less automatic? (I didn't see these points addressed in Jim's linked post; sorry if I missed something.)
-
My understanding is that all the kinks were worked out late Friday, or we would have announced it then.
Chris or I (more likely) will make a blog post sometime tomorrow, if the team agrees we're ready.
The only "pre-requisites" to gaining access are to run the process. You'll need to make an account on the pfSense portal (if you don't already have one), then agree to (and click-through) both the contributor agreement, and the trademark agreement, then put a ssh pubkey in the provided form and submit. Heck, it's possible that if you can follow those directions, you'll have access in the next 30 minutes.
People who violate the agreements are obviously not going to stay in the program.
-
So, just to clarify, that means access will be available to paying customers only?
-
Please go to https://portal.pfsense.org/ and create an account if you don't have one. Note that there is now a $0 'developer' account. Thus, you don't need to be a paying member, though if you already are one, you don't need to create a new account.
Next if you execute the ICA/CCA (pick one) and then the License Agreement, there will a place to put your ssh public key in and, once the sync occurs, you will be able to access the tools repo.
https://portal.pfsense.org/members/signup/ICLA (if you're signing as an individual)
https://portal.pfsense.org/members/signup/CCLA (if you're signing on behalf of a corporation)
https://portal.pfsense.org/members/signup/LAThe only reason we haven't posted about it is that it was late on Friday before we verified everything was working.
The git server pulls the keys from the portal system every 5 minutes, so once you have both agreements checked, and your key in you have access.
(Edit: Obviously, this needs some editing.)
-
I must be missing something… The only options for "membership type" that I see there are "Gold Subscription" ($99/yr), "pfSense Support" ($400/yr) and "pfSense After-Hours Support" ($250/wk). This is on the "subscribe for access" tab, which is where the "signup here" link takes me; I did't see a registration link anywhere else.
-
I guess what you're saying is the URLs you mentioned are used both for creating an account and for signing the agreement?
-
If you sign the ICLA or CCLA first, then the TLA, you should be able to do the rest.
-
Seems to have worked, thanks.
-
So once all that is in place, how do I find out how to actually access the repository? I can't seem to find any pointers to it on the portal side; will I just get an email once my key has been set up?
