Re: [gentoo-dev] Deleting Dead Projects from the Wiki

[Matthew Marchese]

On 9/1/23 15:25, Philip Webb wrote:

230901 Christopher Fore wrote:

I'm currently working with the Wiki team on removing references to Layman

Not quite on your topic, during a recent installation
I noticed that Wiki talks re "burning an ISO to a CD".
My new home-built machine doesn't even have a CD drive
nor could the mobo handle it if it did.
Most install ISOs can now be copied directly onto a USB stick,
which boots & has an install button to click.

Perhaps someone else is handling that part of the clean-up.  HTH.

Yes, we are aware that most systems no longer carry built-in optical 
drives and there is an effort to rework those parts of the Handbook and 
adjust terminology and instructions. At the same time we have several 
*other* areas of the wiki that include for creating bootable media on 
USB: 
https://wiki.gentoo.org/wiki/LiveUSB#Using_dd_to_write_the_ISO_image_to_a_USB_drive


See https://wiki.gentoo.org/wiki/Project:Handbook#Terminology_updates

Update downloadable media terminology from LiveCD/DVD/USB to "live 
image" - https://bugs.gentoo.org/903551


Bad documentation and install for machines without CD - 
https://bugs.gentoo.org/902813


Kind regards,

Maffblaster







OpenPGP_0x7656DA1BCB1ED4F1.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

[gentoo-dev] A couple of new 'features' available on the Gentoo wiki

[Matthew Marchese]

Hi all,

Wanted to document a public service announcement for minor wiki 
enhancements:


1. "Fund me" links are now available on the wiki developer 'profile' 
boxes. You can post a free-form URL to your GitHub Sponsor, Patreon, 
PayPal or another page. I know that I'm very appreciative of all the 
work that people put into making my OS run amazingly, so if you do have 
a method to accept donations I encourage you to post it here. :)


2. Project pages now include an optional link to assigned-bugs at 
bugs.g.o. (closes bug 686264). Of course only works if the project has 
an email address assignment on our Bugzilla.


See the announcement on the wiki here:

https://wiki.gentoo.org/wiki/Main_Page#20220804

I historically haven't written to the mailing lists much, but if this is 
well received I'll try better to keep everyone in the loop on wiki 
changes (as infrequent as they are!). If you see something that's 
terrible, please let me know.


Thankful for you all!

maffblaster

Re: [gentoo-dev] [PATCH 0/1] Add 'notes' element to metadata.xml (GLEP 68)

[Matthew Marchese]

On 10/5/21 12:09, Michał Górny wrote:

On Tue, 2021-10-05 at 19:27 +0100, Sam James wrote:

This is a preliminary version/draft of a proposed change to
GLEP 68.

I'd like to introduce a method for developers to signal anything
special about a package and how to correctly maintain it.

Sam James (1):
   glep-0068: Add notes element for package maintenance instructions

  glep-0068.rst | 26 +++---
  1 file changed, 23 insertions(+), 3 deletions(-)


To be honest, I don't think adding it to metadata.xml is a good idea.
This is not something that's going to be machine-parseable,
and expecting people to look into metadata.xml to see if it's even
present is a bit much.

Maybe we could just add README files to the package directories
in question.  This would have the clear advantage that the files will be
immediately visible.

Some of the devs use their username or project pages on the wiki for 
maintainers notes. That's a decent place to keep them since there is not 
an in-source place, but truly the closer the documentation can be kept 
to the source the better.


I also like the idea of markdown files or RST files living in gentoo::. 
I personally find RST to be a bit more challenging to write, but it's 
simple enough to learn and we 'already have RST to HTML conversion on 
www.g.o for GLEPs. GitHub will render either file format in browser. Not 
sure about all the other Git* sites.


Apparently the MD and RST formats are somewhat interchangeable if one 
does not go too crazy on formatting: 
https://gist.github.com/javiertejero/4585196

Re: [gentoo-dev] New package neomutt

[Matthew Marchese]

On 07/31/2017 03:52 AM, Fabian Groffen wrote:
> On 31-07-2017 04:55:58 -0500, Matthew Thode wrote:
>> On 17-07-31 09:11:19, Nicolas Bock wrote:
>>> Hi,
>>>
>>> I would like to add neomutt to the tree. This new package is meant 
>>> as an alternative and not a replacement of the existing mutt 
>>> package.
>>>
>>> Thanks,
>>>
>>> Nick
>>>
>>> -- 
>>> Nicolas Bock 
>>
>> It was my understanding that neomutt was mainly mutt with a bunch of
>> patches added on, from what I can see, those patches are already handled
>> by use flags in the mutt package itself.
>>
>> https://www.neomutt.org/about.html describes itself as a large set of
>> feature patches and not a fork as well.  Are there missing patches that
>> need to be added to the mutt package?
> 
> These days NeoMutt really is a fork, with a complete code-re-indent,
> function name changes, etc.[1]  They move fast, deviating from Mutt and
> no longer submit patches to Mutt.  It remains to be seen where both
> projects end up, IMO.  It is no longer feasible to add features from
> NeoMutt to Mutt, and Mutt moves along its own path (with
> features/improvements) as well.
> 
> For now it seems useful to me to have both mutt and neomutt around.  I
> sent my detailed comments on the neomutt ebuild to Nicholas off-list
> already.  The changes suggested should show even more how the two are
> different.
> 
> Thanks,
> Fabian
> 
> [1] 
> http://mailman.neomutt.org/pipermail/neomutt-devel-neomutt.org/2017-April/000364.html
> 
I second Fabians input here. Two packages are necessary.



signature.asc
Description: OpenPGP digital signature

Re: [gentoo-dev] Rekindling Gentoo News

[Matthew Marchese]

On 01/15/2017 01:36 AM, Michał Górny wrote:

> On Sat, 14 Jan 2017 23:41:16 -0800
> Matthew Marchese <maffblas...@gentoo.org> wrote:
>
>> I'm not looking to spend a lot of time doing that. I have something much
>> simpler in mind. Presently the GMN project has moved. It is now called
>> simply "News". We have a #gentoo-news channel on Freenode and a
>> n...@gentoo.org mail alias.
> To be honest, I think this name is a bit confusing. When I've seen
> the topic of this e-mail, I thought it will be about news items (as
> in those going through 'eselect news')... But if it's too late to
> change, I guess we can get used to it.
>
I messed up and accidentally cross-mailed -project- and -dev lists.

For anyone else who replies, please do so on -project.  Sorry!

[gentoo-dev] Rekindling Gentoo News

[Matthew Marchese]

Hi all,

Huzza! Welcome to 2017! This year I would like re-ignite the Gentoo news
project. It has been smoldering for some time and I think with a small
bit of interaction from YOU (the developers, the  council members, and,
yes, even YOU foundation members), it would be easily rekindled.

To be clear, I have no absolutely no intention of writing a full
newsletter each month. Most people's attention spans are not long enough
to even read though a newsletter or make it this far into an email, so
I'm not looking to spend a lot of time doing that. I have something much
simpler in mind. Presently the GMN project has moved. It is now called
simply "News". We have a #gentoo-news channel on Freenode and a
n...@gentoo.org mail alias.

Here is the YOU part: the only way this project will work is if YOU push
news announcements to ME. As you understand, Gentoo is a broad ecosystem
with LOTS going on _constantly_. I only use one desktop environment and
can't look at #gentoo-commits / gentoo.git log to track the changes of
major successes or new additions to the main repo.

You can use either the IRC channel or n...@gentoo.org to push news items
of interest to me. I will handle weeding them out and getting them to
the developers and the community on the social sites. The IRC channel is
preferred because I am always connected, and messages are instant; but
again, as it should be in Gentoo, _your choice_.

Example news items could be:

* New release of Gnome (or any other supported DE).

* New, interesting packages added to the main repo.

* New projects - Tell me about the project goal and what you're working
on. I will also watch the gentoo-project list, but LOTS of times it's
easy to miss things.

* Project changes  - Want the community to test something? Want to warn
us about something? Want to remind us of something? Want to scold
inactive members of your project? You can now do that on social sites so
that the world can see! Hope you caught the sarcasm in that last sentence.

* Event annoucements - Tell me where you're meeting and what you'll
talking about. Give me the highlights of a past the event. Tell me why
attendees should go to your event. Share pictures from your event.
Gentoo is going to be present as FOSDEM 2017. What about Scale? I'd be
happy to push invitations to the social sites. Just tell me what to say.
For event invitations should also have an announcement on the front page
of the main site, IMO, but we can start with getting them to our social
sites.

* Anything that is exciting that has happened for Gentoo - This goes for
projects that completed a long or short term goal, Gentoo being
recognized for something important, or Gentoo is seen somewhere in the
news media. Good OR bad external news can be shared. You can even rip
something off the forums or Reddit and re-share it in #-news.

* Gentoo ported to run on a strange or unusual piece of hardware -
Recently I saw Gentoo being ported to the PS4. That was something that
should be shared with #-news.

Once it gets to me, the news will probably go out one news item at a
time, in one or maybe two sentences. This way we can be reporting news
as it develops, instead of releasing news in a monthly --oneshot like
the old project. As mentioned for event invitations above, larger or
more important news items can hopefully be shared on the main www page.

Also, the QA project seems to be good at generating all kinds of graphs
and charts, so I have no plans to use the old Python scripts for those
kinds of things. I do have some other ideas up my sleeve for this
project in the future.

The one thing to take away from this email: if you have some news item
that has some value to the community you should share it in #-news. It
would be great to release early and release often in terms of news. This
will not happen without YOUR help.

Anyone who wants to aid these efforts welcome to join the project.
Looking forward to hearing any thoughts from you on things that may need
to be flushed out a little.

Your docs doctor and news host,

Mr. Marchese

Re: [gentoo-dev] New project: Handbook

[Matthew Marchese]

On 10/14/2016 03:12 AM, Daniel Campbell wrote:
> On 10/14/2016 01:24 AM, Matthew Marchese wrote:
>> All,
>>
>> After _many_ essential and necessary years of service the Gentoo
>> Documentation Project (GDP) has fulfilled its purpose[1][2] and is in
>> the process of being phased out.
>>
>> As a platform, the wiki has enabled every Gentoo developer (not just
>> those in the Documentation team) and many in the community to maintain
>> Gentoo documentation. All the relevant "HOWTO" articles and other
>> articles produced by former GDP members (and other contributors) have
>> long since moved to publicly editable wiki namespace. These days the
>> community and every Gentoo developer should step up to the plate from
>> time-to-time and maintain the docs.
>>
>> There is very little that is currently "locked down" on the wiki. The
>> Handbook (and everything else in the Handbook namespace) is one
>> exception to what is publicly editable. Since it contains our official
>> and crucial installation instructions; it is a bit risky to put it
>> publicly editable namespace. This creates an inherent 'who's responsible
>> to keep it updated?' So, in order to clarify who will continue to assume
>> responsibility for the Gentoo Handbook, the Handbook project has been
>> newly formed as a sub-project of the Wiki project.  Currently just SwifT
>> and me are in this new project, but anyone who's interested in
>> updating/maintaining the Handbook is welcome to join.
>>
>> Here are our current goals, short and sweet:
>>
>> 1. Actively modernize and maintain the official Gentoo Handbook
>> documentation in the Handbook: namespace.
>> 2. Handle 'marking' the Handbook for translation.
>> 3. Maintain the Handbook Development guide.
>>
>> Comments on these are welcome.
>>
>> Suggestions for Handbook updates or fixes can be left on each page's
>> discussion page. Among other areas of contribution, those who are a part
>> of this project will make it a priority to respond to these queries.
>>
>> I suspect next we'll need an e-mail address separate from the wiki's
>> mail address. Other than that we'll still all hang out in #gentoo-wiki
>> on Freenode and continue advancing Gentoo to a better place. Again,
>> comments are welcome.
>>
>> Kind regards,
>> Maffblaster
>>
>> [1]
>> https://archives.gentoo.org/gentoo-doc/message/892f335a04fb7e372116ca3e6b2d0c84
>> [2]
>> https://archives.gentoo.org/gentoo-doc/message/944b4b36ab3883c6b223a240feb42fb8
>>
>>
> Whatever structure that will allow wiki building to continue and reduce
> any possible confusion is a win in my book.
>
> Devs interested would need to then join the wiki project then, correct?
>
No. They'd only need to directly join the Handbook project.



signature.asc
Description: OpenPGP digital signature

Re: [gentoo-dev] RFC: Dead project cleanup - Merging Presentation with Public Relations

[Matthew Marchese]

On 10/07/2016 04:56 PM, Matthew Marchese wrote:

> Hi all,
>
> Thought I'd send a RFC out to you all to get a little feedback before I
> make any changes to this since I didn't originally start the project. If
> no one responds with a good reason why NOT to make the changes I
> purpose, I will proceed in a somewhat timely manner.
>
> It's been over a year since I manually moved the Presentation Project
> from wwwold to the wiki. No one who was previously involved in the
> project has presumed membership (or leadership) with the project.
> There's only been one meaningful edit by Rich0 to one of the project's
> two subpages. He kindly added links to a Gentoo presentation he recently
> gave.
>
> I currently see no reason why we need a separate project for
> Presentations. Maybe once when Gentoo PR was busier and we had more
> people giving talks it was necessary. If we're just looking for a place
> to host links or files I think merging this project with Public
> Relations will work nicely. I propose hosting the content of this
> project under the Public Relations project, since it has members who are
> actually overseeing it as Project specification (GLEP:39) demands.
>
> Empty projects should be removed. They are dead. It's not me who says
> it, it's GLEP 39. Be mad at it, not me. :P
>
> I already have a repo for PR setup at projects.g.o. I will make a
> presentations/ directory for storing the PDF files that Robin was
> recently looking for...I'll have to dig them out of the Wayback Machine,
> but that shouldn't take me too long.
>
> Your wiki warrior,
>
> Maffblaster
>
> https://wiki.gentoo.org/wiki/Project:Presentation

Okay! I've got all the old stuff dug out of the Wayback Machine. Files
are now hosted under projects.g.o here:

https://projects.gentoo.org/pr/presentations/

Please note the directory naming. I'd like to keep this consistent with
the date following the title of conference in all lower case. Even if
there's only one talk, please keep it this way. I can envision Gentoo
talks having the same exact title.

I will update the links to the wiki page at some point this weekend
(check back in a few days):

 https://wiki.gentoo.org/wiki/Project:Public_Relations/Available_Presentations

Feel free to point to me to places I can get other FOSDEM / Mini conf
stuff... Not sure what we're going to do about video. Upload them to our
YouTube account and/or Archive.org for hosting?

Kind regards,
Matthew

[gentoo-dev] New project: Handbook

[Matthew Marchese]

All,

After _many_ essential and necessary years of service the Gentoo
Documentation Project (GDP) has fulfilled its purpose[1][2] and is in
the process of being phased out.

As a platform, the wiki has enabled every Gentoo developer (not just
those in the Documentation team) and many in the community to maintain
Gentoo documentation. All the relevant "HOWTO" articles and other
articles produced by former GDP members (and other contributors) have
long since moved to publicly editable wiki namespace. These days the
community and every Gentoo developer should step up to the plate from
time-to-time and maintain the docs.

There is very little that is currently "locked down" on the wiki. The
Handbook (and everything else in the Handbook namespace) is one
exception to what is publicly editable. Since it contains our official
and crucial installation instructions; it is a bit risky to put it
publicly editable namespace. This creates an inherent 'who's responsible
to keep it updated?' So, in order to clarify who will continue to assume
responsibility for the Gentoo Handbook, the Handbook project has been
newly formed as a sub-project of the Wiki project.  Currently just SwifT
and me are in this new project, but anyone who's interested in
updating/maintaining the Handbook is welcome to join.

Here are our current goals, short and sweet:

1. Actively modernize and maintain the official Gentoo Handbook
documentation in the Handbook: namespace.
2. Handle 'marking' the Handbook for translation.
3. Maintain the Handbook Development guide.

Comments on these are welcome.

Suggestions for Handbook updates or fixes can be left on each page's
discussion page. Among other areas of contribution, those who are a part
of this project will make it a priority to respond to these queries.

I suspect next we'll need an e-mail address separate from the wiki's
mail address. Other than that we'll still all hang out in #gentoo-wiki
on Freenode and continue advancing Gentoo to a better place. Again,
comments are welcome.

Kind regards,
Maffblaster

[1]
https://archives.gentoo.org/gentoo-doc/message/892f335a04fb7e372116ca3e6b2d0c84
[2]
https://archives.gentoo.org/gentoo-doc/message/944b4b36ab3883c6b223a240feb42fb8

Re: [gentoo-dev] The future of the Sunrise project

[Matthew Marchese]

On 06/07/2016 02:29 AM, Anthony G. Basile wrote:

> Its time to retire the project.  Put out a last call for anyone to adopt
> it.  If not, then freeze commits but leave the repo open as an archive.
> Anyone who wants to scavenge ebuilds from it can do so.
I agree. We should be a better job at trimming the fat in various ways.
I just looked at this project recently and was scared.
-maffy

Re: [gentoo-dev] amd64 and x32 systemd stages should be ready

[Matthew Marchese]

On 5/7/2016 11:52 AM, Andreas K. Huettel wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Am Samstag, 7. Mai 2016, 19:47:55 schrieb Andreas K. Huettel:

Am Samstag, 7. Mai 2016, 17:09:50 schrieb Anthony G. Basile:

Hi everyone,

I've been pushing out systemd stage3s for amd64 and x86 and putting them
under our official releases at [1] and [2].  I think all the bugs are
out and those stages are pretty tight.  The next step is for me to
advertise them at [3].

Great- thank you !!!

And for whoever wants to advertise:


On request (what it "just works" without systemd???), here's the more
symmetric selection of posters:

http://dev.gentoo.org/~dilfridge/poster/gentoo-abducted_A0_choice_2.pdf
http://dev.gentoo.org/~dilfridge/poster/gentoo-abducted_A0_choice_3.pdf

:)

- -- 


Andreas K. Huettel
Gentoo Linux developer
dilfri...@gentoo.org
http://www.akhuettel.de/

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.1

iQJ8BAEBCgBmBQJXLjl/XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDMjhGQ0IwRjdCRUQxMzdBQUNCMDJEODlB
NDRDRjM3M0U3RUU5OUU0AAoJEKRM83Pn7pnkaZ0QANEEM6P6XmsS2FAWnDzdH0lI
FxZv+mVOp8iFjG5qALG2CCDZjHv26R0RqQgvWirs12vuX28gRonB07PzvjieQsus
YcNkNeBxGi8cgoYuEJnN6ROMdJGYq71ZhFZ6QX+5XolDUyuwYIr03aBuAnKDFxLE
oXBcmh1N45qCah3pQzEh6sbYuBDTvgUwTSHaD6XgWsd5Ln4FWmjyJ3c3EOY3wwEA
rdO52of9IJxeuj+6TE4+W5A5V0An0JO/jc8tXzpp7mAKWIFavd9HBQXIUhT9CaOP
du29a3RaM+DeIgSb+eFjED/H1Qo8Bq+QRN3f3RbedUr60F7F1YLtBaG45SRhF1Mi
qUKV2y9YZ7NBZzoCdVOEqDVamGVkY+Z2HACdM6nWscwh9misPWXLXZwAqJE3Dlpo
LHGykFukDZv/6CuX0WhUwPK2doEv7YD1DZ/qTB2WMAVC7N8rQfDMEtrnCMK7Bx42
cU+1aoVKtcQF8Cf6AcH4ijF21+ORxGRxtYpiCy4cQCOxw+hc2d9JyBsQPIBI9pKQ
P4SFT3qcg9+CsY3XYdGFggGwP2dwRhp8AzA69LDdkSa7ObHv1r9gZQgNduCAcjTh
fAJkdFtDd4kRtR5JfNfFwnle6ztnAlCoDNto2edphhlZY6QOnaPjkaKlyb44J894
gGIHyjoXz+5TYzrHO1Xe
=gYyU
-END PGP SIGNATURE-


Looks good. Nice work, fellas.

I'll do some testing of my own on those stage tarballs so that I can 
write some docs, unless you'd like to write them, blueness. This should 
ease the path on the systemd "Handbook extension" idea I've been 
throwing around.

Re: [gentoo-dev] Hardware database

[Matthew Marchese]

On 02/09/2016 07:01 AM, Michał Górny wrote:
> On Tue, 9 Feb 2016 17:53:09 +0300 > agentsmith  wrote: 
> > >> Cool tool i create
ebuild. >> >> On 02/09/2016 05:47 PM, Daniel Campbell wrote:
>
> > Could
>
> On 02/09/2016 05:55 AM, Urbain YANG wrote:  
>  Thank you very much!
> 
>  And wish it will be merged into Portage soon.
> 
> 
>  Urbain YANG urbain.y...@qq.com 
> 
> 
>
> > you
>
> 
>   
> > 在 2016年2月9日，下午9:33，Ponomarenko Andrey
> >  > > 写道：
> >
> > Hello,
> >
> > I have released a new version of the hardware probe tool — HW
> > Probe 1.0, that supports Gentoo and some other popular Linux
> > distributions. The "probe" is a snapshot of the hardware state
> > including a list of devices on board and system logs. The primary
> > purpose of the tool is to share the probe of the computer with
> > developers or other users for the collaborative debugging of
> > hardware problems on it.
> >
> > All probes are uploaded to the central database at
> > http://linux-hardware.org/ that holds probed information in a
>
> > please
>
> > structured form. You can find, for example, in which computer
> > models is presented some device, what driver was used and how it
> > was configured. You can check for failures in logs related to a
> > problem device and so on.
> >
> > The source code of the tool is available here:
>
> > stop
>
> > https://github.com/linuxhw/hw-probe
> >
> > Thank you.
> >  
> If nobody's already started doing the work, one could file a bug on
> our tracker and request an ebuild to be written. Or one could read the
> devmanual and put one together. If someone is interested in
>
> > replying
>
> maintaining that ebuild, one of our proxy-maintainers may be
> interested in helping. Check it out some time. :)
>
> https://bugs.gentoo.org
> https://devmanual.gentoo.org
>
>
>>>  > > in random positions? >

No need for trolling. :P

I like this idea. Having a way to check what drivers were used on a
certain make/model will be helpful for me in the future.

Re: [gentoo-dev] [RFC] Rebooting the Installer Project

[Matthew Marchese]

NP,

You bring about some good points. stager still start with command-line 
interface that can either pass values via command-line options + arguments or 
via 'profiles' which are .ini formatted text files with values predefined. The 
name 'profile' is subject to change because I don't want to confuse new users 
with system profiles, which would also be able to get set...

The web interface, if it ever happens, will come some time after the cli.

The goal of the web interface would allow for unattended graphical installs. 
It would perform almost like the old GLI did: go through a step by step process 
of setting a configuration (or simply point it to a predefined .ini file), 
click install and walk away. As long as the user knows what hardware is on 
his/her system, they should be able to configure things correctly. Just start 
up the server before you walk away and can set all the parameters for the 
install in a web page.

The priorities of the project would be this order:

1) Seasoned users
* Saving time creating backups, recovering, or installing new systems
* Providing an install framework. It seems many Gentoo users have their own 
set of scripts for backups, installation, etc. stager could provide a base for 
those who have not been taking simple system backups. 
2) New users
* New users would still need to read the Handbook in order to learn how Gentoo 
works and to properly configure the installer.
* In some ways I would like the installer to be a teaching tool that will help 
people get their feet wet with our great OS.

maffblaster

On 07/18/2015 04:06 PM, hasufell wrote:
 On 07/18/2015 09:36 PM, NP-Hardass wrote:
 On Sat, 18 Jul 2015 12:01:48 -0700
 Matthew Marchese maffblas...@gentoo.org wrote:

 Hello all,
 I have recently pressed the reboot button on the ol' Installer
 project. I've been able to talk to quite a few developers one-on-one
 via IRC concerning my plans. Most seem to be in support of Gentoo
 having a official installer (the biggest concern is appears to be
 how things will be implemented and the amount of features involved).
 This e-mail is to fulfill GLEP 39's request for comments (RFC),
 concerns, requests, etc. Since I'm a little new to the project I'm
 coming with a bit of ignorance; I know the previous Installer project
 fostered mixed feelings.
 If you'd like to review before replying you can see the Wiki page and
 find the source on GitHub: https://github.com/gentoo/stager
 To summarize I'm writing it in pure Python 3. It first will be able
 to create full backups (stage 4s) and recoveries. After that is
 finished I plan to move on to installations. There will potentially
 be a web interface UI for it. Others are free to create other
 front-ends; to me a web UI makes the most sense and would probably
 require the least deps.
 I'd like to hear it all so please speak your mind. Looking forward to
 hearing from you.
 maffblaster



 Who is your target audience?  New users?  Experienced users?  Not so
 much a comment about your installer, but installers in general, I feel
 the handbook is critically important to helping new users to understand
 Gentoo.
 The handbook consists of different sections. Installation is only one of
 them. An installer would just replace that part, not the others.

 Greatly aiding the fresh install process. stager will not
 remove the need for reading through the Handbooks, but rather work
 along side the handbook in order to help users install Gentoo.

 Can you elaborate on this?  I have trouble envisioning an automated 
 installer process that requires working along side the handbook.

 See above.

[gentoo-dev] [RFC] Rebooting the Installer Project

[Matthew Marchese]

Hello all,

I have recently pressed the reboot button on the ol' Installer project. I've been able to 
talk to quite a few developers one-on-one via IRC concerning my plans. Most seem to be in 
support of Gentoo having a official installer (the biggest concern is appears 
to be how things will be implemented and the amount of features involved). This e-mail is 
to fulfill GLEP 39's request for comments (RFC), concerns, requests, etc. Since I'm a 
little new to the project I'm coming with a bit of ignorance; I know the previous 
Installer project fostered mixed feelings.

If you'd like to review before replying you can see the Wiki page and find the 
source on GitHub: https://github.com/gentoo/stager

To summarize I'm writing it in pure Python 3. It first will be able to create 
full backups (stage 4s) and recoveries. After that is finished I plan to move 
on to installations. There will potentially be a web interface UI for it. 
Others are free to create other front-ends; to me a web UI makes the most sense 
and would probably require the least deps.

I'd like to hear it all so please speak your mind. Looking forward to hearing 
from you.

maffblaster