FFLib moves to Community Ownership

The FFLib Apex Common and ApexMocks open source libraries have become very popular with the Salesforce developer community, with many and diverse uses and a significant number of active contributors. Recognising this level of engagement, the time has come to share responsibility for the maintenance and future direction of the libraries with the developer community. The libraries have therefore been moved to a new GitHub organization, jointly owned by key contributors from the developer community. This change will allow FFLib to better fulfil the needs of the existing users, and ultimately be of value to an even wider audience. This is an important milestone in FFLib's journey and an exciting time for users and contributors alike!

FAQ

Q: Do you plan to change any of the API signatures?

A: No, backwards compatibility is still really important; the "fflib" prefix will remain.

Q: Will all my blog and other links still work?

A: Yes, GitHub manages redirects.

Q: What are your immediate plans?

A: We plan to invite contributors to join in supporting in reviewing PR’s and managing the future of the library taking into consideration community feedback. After this we will get started on some housekeeping items, such as updating the API version and adopting the Source format of DX. We will list these as open issues so everyone can comment on these along with other priorities.

Q: Who will be the initial set of contributors and what’s the process?

A: We have been reviewing the most active past and present contributors, as well as those who help promote the library and best practices around it in various ways such as through events like Dreamforce and participation in DUG’s. Basically the libraries' domain experts! We need to get an initial set of contributors established, but after that the group will self-organize with respect to membership.

Q: Whats next?

A: There has been some great complementary advancements in the platform, such as SFDX, Unlocked Packages and support for enforcing object and field level security that we would like to explore with the community.