Closed aspiers closed 5 years ago
Indeed, it relates to Mautic.org. The branches are currently being used and when the site deploys I would expect we would merge to master and remove anything not being used, at which point the readme file can be updated to give direction on how to be involved with the website team.
On Sun, 2 Jun 2019, 14:41 Adam Spiers, notifications@github.com wrote:
IIUC, there are two websites:
- https://www.mautic.org/ - the FOSS community site
- https://www.mautic.com/ - the commercial site owned and run by Mautic, Inc. / Acquia
I assume that this repository is only concerned with mautic.org, but I think it's important to clarify that. I suggest updating the README and also renaming the repository to https://github.com/mautic/mautic.org. The rename should not break anything since GitHub would automatically set up redirects.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/mautic/website/issues/95?email_source=notifications&email_token=AAWLPIK6CGHYZITBN3AHHP3PYPE2LA5CNFSM4HSCVRJKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GXEVHUA, or mute the thread https://github.com/notifications/unsubscribe-auth/AAWLPIOLP2QYFKCCZ42S5LTPYPE2LANCNFSM4HSCVRJA .
Thanks Ruth. If the expectation is to merge into master
(rather than force-push), is there any reason not to update the README right away?
To clarify, I could submit a simple PR just changing the README to clarify that this repo relates to mautic.org. The directions on how to be involved could come later.
The Mautic organisation this repo belongs to us the Mautic.org one, there is a separate organisation for the commercial side.
Certainly something that can be taken into account to make it clear how people can get involved though once things are clearer regarding the website, thanks for flagging it.
On Sun, 2 Jun 2019, 18:05 Adam Spiers, notifications@github.com wrote:
To clarify, I could submit a simple PR just changing the README to clarify that this repo relates to mautic.org. The directions on how to be involved could come later.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/mautic/website/issues/95?email_source=notifications&email_token=AAWLPINKLL2VTICKB4JDDOTPYP4WDA5CNFSM4HSCVRJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWXZ2TI#issuecomment-498048333, or mute the thread https://github.com/notifications/unsubscribe-auth/AAWLPIIEPRFRDCTTZOOFJCLPYP4WDANCNFSM4HSCVRJA .
OK, I've submitted #96 to address this. This will still allow merging from the other branches to master when they are ready.
IIUC, there are two websites:
I assume that this repository is only concerned with mautic.org, but either way I think it's important to clarify. I suggest updating the README and also renaming the repository to https://github.com/mautic/mautic.org, or https://github.com/mautic/mautic.com if my assumption is wrong. The rename should not break anything since GitHub would automatically set up redirects.