On Mon, Mar 27, 2017 at 9:34 AM, Albert Astals Cid <aa...@kde.org> wrote: > El diumenge, 26 de març de 2017, a les 20:26:25 CEST, A. Bikadorov va > escriure: >> On 26.03.2017 20:17, Albert Astals Cid wrote: >> > El diumenge, 26 de mar� de 2017, a les 18:41:00 CEST, A. Bikadorov va >> > >> > escriure: >> >> On 26.03.2017 18:36, Boudhayan Gupta wrote: >> >>> Write it in a wiki page? >> >>> >> >>> Freundliche Gr��e >> >>> Boudhayan Gupta >> >>> KDE e.V. - Sysadmin and Community Working Groups >> >>> +49 151 71032970 >> >>> >> >>> On 26 March 2017 at 18:33, Albert Astals Cid <aa...@kde.org> wrote: >> >>>> El diumenge, 29 de gener de 2017, a les 8:32:21 CEST, Ben Cooksley va >> >>>> >> >>>> escriure: >> >>>>> Hi everyone, >> >>>>> >> >>>>> We've just completed the registration of all mainline repositories >> >>>>> (not including Websites or Sysadmin namespaced ones) on Phabricator. >> >>>>> Thanks go to Luigi Toscano for providing significant assistance with >> >>>>> this process. >> >>>>> >> >>>>> From this point forward, communities should be moving away from >> >>>>> Reviewboard to Phabricator for conducting code review. Sysadmin will >> >>>>> be announcing a timeline for the shutdown of Reviewboard in the near >> >>>>> future. >> >>>>> >> >>>>> Projects which haven't yet looked into Phabricator, including getting >> >>>>> things like mailing list notifications and projects setup should do so >> >>>>> as soon as practical. >> >>>>> >> >>>>> As part of the registration process, Sysadmin tagged repositories, >> >>>>> associating them to Projects. These tags show what a repository is >> >>>>> associated with and it's status. >> >>>>> >> >>>>> This includes things like whether development is currently active (the >> >>>>> Historical Archival and Up For Adoption tags), which release unit it >> >>>>> is part of (KDE Applications, Frameworks, etc) and the general >> >>>>> development effort it is associated with. >> >>>>> >> >>>>> It would be appreciated if everyone could please check their >> >>>>> repositories to ensure they've been tagged correctly. Adjustments can >> >>>>> either be sent as replies to this email (include sysadmin@ in CC >> >>>>> please) or by asking a member of the Community Admins project on >> >>>>> Phabricator to make the change for you. >> >>>> >> >>>> I tried using arc today, after reading some documentation it seems i >> >>>> need >> >>>> to use >> >>>> >> >>>> arc diff >> >>>> >> >>>> to upload a patch, but then i got hit by >> >>>> >> >>>> >> >>>> $ arc diff >> >>>> Usage Exception: This command requires arc to connect to a Phabricator >> >>>> install, but no >> >>>> >> >>>> Phabricator installation is configured. To configure a Phabricator URI: >> >>>> - set a default location with `arc set-config default <uri>`; or >> >>>> - specify `--conduit-uri=uri` explicitly; or >> >>>> - run `arc` in a working copy with an '.arcconfig'. >> >>>> >> >>>> And i couldn't find more documentation on how to move forward. >> >>>> Ultimately >> >>>> I >> >>>> asked Aleix that told me "copy the .arcconfig file from >> >>>> plasma-desktop". >> >>>> >> >>>> Since newbies usually don't have Aleix at hand, how do we fix this? >> >>>> >> >>>> Cheers, >> >>>> >> >>>> Albert >> >>>>> >> >>>>> Thanks, >> >>>>> Ben Cooksley >> >>>>> KDE Sysadmin >> >> >> >> Which is already done? >> >> -> https://community.kde.org/Infrastructure/Phabricator#Connecting_to_KDE >> > >> > No, sorry, that doesn't work, it links to the calligra .arcconfig, which >> > has "project.name" : "Calligra" >> > What would I write there? >> > >> > Cheers, >> > >> > Albert >> >> >> >> Cheers >> >> Alex >> >> The name of the project for this repo. Sorry, but isn't that pretty obvious? > > No, it is not, let's say that > https://phabricator.kde.org/source/plasma-framework/ > did not have an .arcconfig file > > Should i use plasma.framework? > Should i use "Plasma Framework"? > Should I use "Plasma Framework (Library)"? > And most importantly, what does that project.name do?
You should not need to set project.name in .arcconfig. When Arcanist creates a revision (review) it should associate it with the appropriate repository on Phabricator. That in turn will trigger Herald to add any necessary projects and other subscribers - resulting in mails going out to mailing lists, project maintainers and so forth. Creation of Herald rules is restricted to Community Admins as global rules have the power to bypass all access controls and can be used to perform significant actions (bulk subscribing others, etc) Please see https://phabricator.kde.org/H19 for the rule for Plasma. > > Because if you actually look at the plasma-framework .arcconfig you'll see it > doesn't have a project.name > > I sincerely think that Luigi's suggestion is what should be in > https://community.kde.org/Infrastructure/Phabricator#Connecting_to_KDE > or at least as an alternative way. > > Cheers, > Albert Cheers, Ben > >> The wiki says its a template and if you are unsure, you can look up the >> project name on Phabricator. >> >> Cheers >> Alex > >
