Hi Valorie!
On Sat, Dec 28, 2019 at 1:36 PM Valorie Zimmerman <
valorie.zimmer...@gmail.com> wrote:
> By the way, the Frameworks Cookbook was written and is still available:
> https://community.kde.org/Books for more information. And we did do it in
> git!
>
Thanks! This and the much older devel
On Sat, Dec 28, 2019, 08:39 Olivier Churlaud wrote:
> Hi,
>
> At CERN we didn't speak about this, except with the Plasma team who spoke
> about having a cookbook based on git containing all the code and
> explanations.
>
> Sebastian Klüger was the one who raised the idea. I have no idea if
> some
up and organizing the wikis now takes a lower priority.
>That
>> said,
>> > certain aspects like guides for new contributors and external
>developers
>> > are just as or even more important now than ever.
>> >
>> > 4. Since many parts of the developer docu
On Fri, Dec 27, 2019 at 10:39 PM Carl Schwan wrote:
> It shouldn't be very difficult to create a MediaWiki plugins that embed a
> specific file from git in a MediaWiki page. We already have an extension
> for Bugzilla integration, so it is possible. But before trying to solve the
> technical deta
ontributors and external developers
> > > are just as or even more important now than ever.
> > >
> > > 4. Since many parts of the developer documentation, particularly those
> > > related to Frameworks, might be in a period of transition or rapid change,
>
Hi Carl,
Thank you for the response!
On Wed, Dec 25, 2019 at 5:59 AM Carl Schwan wrote:
> Hi,
> thanks for the report. An issue I see currently is that we have three
> entries for our KDE frameworks and developer utilities:
>
> 1. https://kde.org/develop
> 2. https://kde.org/products/frameworks
ground before having writers deal with different
> systems
> > and software. The Wikis are perhaps suited for this kind of workflow.
> >
> > These are just some of the high-level points from the two reports and
> those
> > documents contain more precise suggestions fo
tware. The Wikis are perhaps suited for this kind of workflow.
> >
> >
> > These are just some of the high-level points from the two reports and those
> > documents contain more precise suggestions for the next actions to take.
> > Again, I apologize to the
for so long and I
> am very excited to get it rolling again. Let's make KDE and its developer
> documentation rock even more!
>
> Attached files:
>
> 1. 01 KDE Developer Documentation Update Project Report.pdf
> 2. 02 KDE Developer Documentation Report Update - 2019-12-09.pdf
the ball for so long and I
> am very excited to get it rolling again. Let's make KDE and its developer
> documentation rock even more!
>
> Attached files:
>
> 1. 01 KDE Developer Documentation Update Project Report.pdf
> 2. 02 KDE Developer Documentation Report Update - 2019-12-09.pdf
>
>
On Fri, Mar 29, 2019 at 3:11 AM Olivier Churlaud
wrote:
> I started porting some tutorials to the repos where they belongs as
> examples (for instance KWallet (https://phabricator.kde.org/D14955) and
> KMessageBox (https://phabricator.kde.org/D14957).
That's awesome! Thanks for getting this st
Hi Juan Carlos,
Le mercredi 27 mars 2019, 14:03:54 CET Juan Carlos Torres a écrit :
> Greetings KDE Community!
>
> I'm Juan Carlos Torres (Jucato on IRC) and I've recently been hired as a
> contractor to get the ball rolling on updating our developer documentation.
> Over the years, our community
Greetings KDE Community!
I'm Juan Carlos Torres (Jucato on IRC) and I've recently been hired as a
contractor to get the ball rolling on updating our developer documentation.
Over the years, our community has produced an incredible wealth of
knowledge that now needs our attention and love. While th
13 matches
Mail list logo
