Privacy "cutting edge" Addon for JCB #429
Labels
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: joomla/Component-Builder#429
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Steps to reproduce the issue
Feature Request to add the GDRP integration to all related components build with JCB.
Expected result
I think this must be a "paid option" , so when you sponsor JCB for $100 or more you can get access to it.
Actual result
@Llewellynvdm I am willing to help brainstorm and code some of this, I have some great ideas that will not only give JCB more scope for 3rd party integration, but also making it possible to sell new compiler features. (so I will private message you this)
System information (as much as possible)
Will work for all components build with JCB
Additional comments
To provide easy integration options with JCB via plugin events, and then to use those events to provide for all components build with JCB Integration to the new privacy component of Joomla.
@marcodings and I was talking about this, just the other evening. So sure lets see what can be done, I have read over the plugin requirements, and it all seems straightforward.
So lets do this! I am always open to these kind of ideas! Specially if we can get some more sponsors 👍
I would argue that any core feature of joomla should be "free". Unfortunately time is not free. Until this project grows and gains traction to be supported by more developers any new functionality would fall to JCB-core developers. I see more people getting involved (as myself) in helping in other needed areas, however the total burden is still to much to bear with the things to do as J4?
I would argue to make this and future core features "donation" based, giving earlier access to project contributors and financial donors to the added features and the such, With the functionality basically coming to all. I you require the cutting edge either wait "a year?" or contribute/donate.
On top of this i would suggest to consider a "crowd funding" campaign with a set goal to start development and a total goal to complete it.
For future viability i would also consider splitting of none joomla core functionality as buyable addons (if techically possible). Top of my hat i think of pending "crowdin" support for translation, "release" support such a WHQM and asked ARS. I'm sure we can find more
my 2ct
marco
@marcodings you have a point, and so let look at this option:
I would vote that those who are listed here count as contributors.
My vote also includes guys like @marcodings, @peterpetrov and other who has been contributing in the unseen 👍
I think once we have this feature ready, we will setup a form on JCB website where request can be made for access, and the motivation/reason that person feels they are eligible to access can then be fine tuned. For now lets focus on the feature, and all its requirements.
Okay some of the first steps is to add events all over the compiler, so we can target areas via a plugin. I have started with this. I am first take small steps here, since once these events are added we will need to keep them intact, so any help in terms of advice and direction to best practice and implementation on this will be great. Here is the list of my first few events, and I am only now in the Fields class, started in the Get class.
I think there are still many to follow...
Okay so I have now added over 40 events to the compiler ,and here is a plugin to start testing this major improvement, there is more to come and all is not yet stable, but give it a go and let me know.
The plugin:
plg_componentbuildercompilerevents_1.0.1.zip
Looking over this list, give me more ideas!
struggling to see how to "test" this in real life without knowing what i would want "to do to the compiler"