Short status updates weekly/biweekly
by Anil Saldhana
Hi all,
we are going to have frequent checkpoint releases and
documentation/quickstarts updated. This gives a good avenue for people
to provide feedback and ask questions/try software.
Given this, in consultation with various folks, we feel that folks
working on security projects to send status blasts to this mailing list
once a week or biweekly as to what they are working on and what is
proposed next. This will improve synchronization between the teams who
consume security code and who develop security code.
Pedro and I are going to email this list with what we are doing.
Should we do weekly or biweekly?
Who else?
Regards,
Anil
11 years, 6 months
PicketLink restructure
by Shane Bryzak
In the interests of presenting a clear message to our developers, one of
the steps we'll be taking is to consolidate the various PicketLink
projects into a single project and presenting this as the "go to"
solution for application security. For now I've merged the CDI and IDM
subprojects (these are now submodules of the PicketLink project, with
"CDI" renamed to "Core") and the plan is to eventually merge the social
and federation modules also.
You can find the new GitHub repository here:
https://github.com/picketlink (renamed from picketlink-cdi) and the
picketlink-idm repository has now been deleted. For anyone working on
these modules, please use the new repository from now on.
Thanks!
Shane
11 years, 6 months
PicketLink projects need to be brought back
by Anil Saldhana
As project founder and lead of PicketLink, I would like projects back to
where they were on Friday. I will not allow loss of code and history
done by me or any of my team members. Until this is sorted, please
consider not making changes to PicketLink on github.
We need to have a call soon on the modules.
11 years, 6 months
