Re: Fedora 35 release notes are now open!
Leslie S Satenstein <[email protected]> Tue, 12 Oct 2021 20:57:29 +0000 (UTC)
| Newsgroups | gmane.linux.redhat.fedora.documentation |
|---|---|
| Message-ID | <[email protected]> |
--===============2903380277871706374==
Content-Type: multipart/alternative;
boundary="----=_Part_2344802_1111444170.1634072249127"
------=_Part_2344802_1111444170.1634072249127
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Sarah and others.
Not having all access, I was able to download and edit/validate the followi=
ng=C2=A0 from
(Rawhide version) =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 install-guide/modules/install-guide/pages/insta=
ll
I have walked through, validated and edited the following
rw-rw-r-- 1 leslie leslie=C2=A0 7602 Oct 10 16:31 After_Installation.adoc
-rw-rw-r-- 1 leslie leslie=C2=A0 6231 Oct 10 16:52 Booting_the_Installation=
.adoc
-rw-rw-r-- 1 leslie leslie 11774 Oct 11 21:42 Installing_Using_Anaconda.ado=
c
-rw-rw-r-- 1 leslie leslie 16164 Oct 11 22:40 Preparing_for_Installation.ad=
oc
-rw-rw-r-- 1 leslie leslie 25895 Oct 12 12:37 Troubleshooting.adoc
I cannot update the git repository, which because I do not have update acce=
ss,=20
I need some help with Andora or other tools to print my updates, so I can s=
hare=C2=A0 what I have done
Again, there were many hours contributed to correcting grammar and phrasiol=
ogy
Is anyone, willing to accept an email with my updates as an attachment
I prefer to make these 5=C2=A0 adoc files available for someone to print ou=
t=20
I can create a tar file, and put that tar file onto a google drive, onto dr=
opbox, so that someone more familar with Fedora's *adoc=20
Regards=20
=C2=A0Leslie
Leslie Satenstein
Montr=C3=A9al Qu=C3=A9bec, Canada
=20
On Tuesday, October 12, 2021, 12:25:30 p.m. GMT-4, Sarah Finn <sfinn@re=
dhat.com> wrote: =20
=20
Great stuff Petr!=C2=A0
On Thu, 7 Oct 2021 at 21:26, Petr Bokoc <[email protected]> wrote:
Hi everyone,
Fedora 35 Beta is out now[0], so it's time to start writing release notes o=
nce again!
As usual, we aim to cover notable Changes[1]. Ben Cotton has been tracking =
those in our release-notes issues for us, which allows us to grab a list of=
everything that needs to be documented[2]. Branch *f35* is ready for your =
pull requests.
=3D What to do
1. Pick one or more issues in the list linked above.
2. Open each issue you picked, and click the Take button on the right to cl=
aim it. (If you claim an issue but later find out you don't have time to wr=
ite about it, remove yourself from the issue ASAP so others can see it's fr=
ee and take it!)
3. Find some information about the issue. A lot of them have plenty of info=
in them already; if not, find out who's responsible for the change, and ta=
lk to them on IRC or via mail. Of course it's always better if you try to d=
o research before you ask questions. Note that you might not always be able=
to reach the owner in a reasonable timeframe; in that case just do your be=
st, I'll be reviewing PRs, so if we publish something wrong, it's on me.
4. Write a release note about the issue. If you're not sure how exactly a r=
elease note looks, check out some of the previous releases for inspiration.=
We don't want any long, overly technical texts, the release notes are gene=
rally meant to highlight changes, not to tell people how to use something.
5. Now the workflow diverges based on your permissions and technical skills=
:=C2=A0=C2=A0
=C2=A0=C2=A0=C2=A0 5a. If you know how to use git and asciidoc, we'd apprec=
iate it if you wrote up the release note and sent a pull request against th=
e main repo, branch "f35". Your contributions should go into one of the fil=
es in "modules/release-notes/pages/", which one exactly depends on the cont=
ents of the change you're documenting. Use the "build.sh" and "preview.sh" =
scripts in the repository root to preview your changes locally; see the rep=
ository README for specific instructions. If you can't see the section wher=
e you added your contributions at all, make sure it's included in "modules/=
release-notes/nav.adoc".
=C2=A0=C2=A0=C2=A0 5b. If the above sounds like gibberish to you, it's fine=
: just add a comment with your text into the issue, and ping me on IRC/Tele=
gram/Matrix or through e-mail[3]; I'll mark it up for you and make sure you=
r contribution appears in the final document.
See also our contributor docs[4] for some additional info and tips; especia=
lly the "Git for docs writers" section if you're not familiar with the syst=
em.
If anyone has any questions, go ahead and ask either here on the list or on=
IRC, I'm happy to help. The current schedule shows the preferred final rel=
ease target on *October 19*, which gives us about 2 weeks to work with, whi=
ch really isn't much. The release date may slip, but don't count on it.
Happy writing!
Petr
[0] https://fedoramagazine.org/announcing-fedora-35-beta/
[1] https://fedoraproject.org/wiki/Releases/35/ChangeSet
[2] https://pagure.io/fedora-docs/release-notes/issues?status=3DOpen&search=
_pattern=3DF35&close_status=3D
[3] https://docs.fedoraproject.org/en-US/fedora-docs/#find-docs=20
[4] https://docs.fedoraproject.org/en-US/fedora-docs/______________________=
_________________________
docs mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-o=
f-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/[email protected]=
oraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infra=
structure
--=20
Sarah=C2=A0Finn
She/Her
Senior Agile Practitioner
Agile DevOps CoP Manager
Red Hat
Waterford, Ireland
[email protected]=C2=A0 =C2=A0
M:=C2=A00879830832=C2=A0=C2=A0 =C2=A0
@RedHat=C2=A0=C2=A0=C2=A0Red Hat=C2=A0=C2=A0Red Hat
| |
|=20
|
"If you are not willing to risk=C2=A0the usual, you will have to settle for=
the ordinary."_______________________________________________
docs mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-o=
f-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/[email protected]=
oraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infra=
structure
=20
------=_Part_2344802_1111444170.1634072249127
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<html><head></head><body><div class=3D"ydpe35a5c30yahoo-style-wrap" style=
=3D"font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px=
;"><div><div dir=3D"ltr" data-setdir=3D"false">Sarah and others.</div><div =
dir=3D"ltr" data-setdir=3D"false"><br></div><div dir=3D"ltr" data-setdir=3D=
"false">Not having all access, I was able to download and edit/validate the=
following from<br></div><div dir=3D"ltr" data-setdir=3D"false">(Rawh=
ide version) &n=
bsp; install-guide/modules/install-guide/pages/install</d=
iv><div><br></div><div dir=3D"ltr" data-setdir=3D"false">I have walked thro=
ugh, validated and edited the following</div><div dir=3D"ltr" data-setdir=
=3D"false"><br></div><div dir=3D"ltr" data-setdir=3D"false"><div>rw-rw-r-- =
1 leslie leslie 7602 Oct 10 16:31 After_Installation.adoc<br>-rw-rw-r=
-- 1 leslie leslie 6231 Oct 10 16:52 Booting_the_Installation.adoc<br=
>-rw-rw-r-- 1 leslie leslie 11774 Oct 11 21:42 Installing_Using_Anaconda.ad=
oc<br>-rw-rw-r-- 1 leslie leslie 16164 Oct 11 22:40 Preparing_for_Installat=
ion.adoc<br>-rw-rw-r-- 1 leslie leslie 25895 Oct 12 12:37 Troubleshooting.a=
doc<br><div><br></div><div dir=3D"ltr" data-setdir=3D"false">I cannot updat=
e the git repository, which because I do not have update access, <br></div>=
<div dir=3D"ltr" data-setdir=3D"false"><br></div><div dir=3D"ltr" data-setd=
ir=3D"false">I need some help with Andora or other tools to print my update=
s, so I can share what I have done</div><div dir=3D"ltr" data-setdir=
=3D"false"><br></div><div dir=3D"ltr" data-setdir=3D"false">Again, there we=
re many hours contributed to correcting grammar and phrasiology</div><div d=
ir=3D"ltr" data-setdir=3D"false"><br></div><div dir=3D"ltr" data-setdir=3D"=
false">Is anyone, willing to accept an email with my updates as an attachme=
nt<br></div><div dir=3D"ltr" data-setdir=3D"false"><br></div><div dir=3D"lt=
r" data-setdir=3D"false">I prefer to make these 5 adoc files availabl=
e for someone to print out <br></div></div><div dir=3D"ltr" data-setdir=3D"=
false">I can create a tar file, and put that tar file onto a google drive, =
onto dropbox, so that someone more familar with Fedora's *adoc <br></div></=
div><div dir=3D"ltr" data-setdir=3D"false"><br></div><div dir=3D"ltr" data-=
setdir=3D"false"><br></div><div dir=3D"ltr" data-setdir=3D"false"><br></div=
><div class=3D"ydpe35a5c30signature"><div><div><div><div><div><div><div><sp=
an lang=3D"FR-CA">Regards</span> <div><b><font size=3D"2"><br></font><font=
size=3D"2"> Leslie</font><br></b></div> <div><font color=3D"green"><b=
><font size=3D"1">Leslie Satenstein</font></b></font><font style=3D"color:r=
gb(191, 0, 95);" size=3D"1" color=3D"green"><span style=3D"font-weight:bold=
;"></span></font><br></div><font size=3D"2" color=3D"green"><b>Montr=C3=A9a=
l Qu=C3=A9bec, Canada</b><br></font><br><font size=3D"1" face=3D"lucida con=
sole, sans-serif"><b id=3D"ydpe35a5c30yui_3_13_0_ym1_1_1391351152837_28311"=
><font id=3D"ydpe35a5c30yui_3_13_0_ym1_1_1391351152837_28310" color=3D"blac=
k"><span id=3D"ydpe35a5c30yui_3_13_0_ym1_1_1391351152837_28309" style=3D"fo=
nt-weight:bold;font-size:13.5pt;color:black;"></span></font></b></font></di=
v></div></div></div></div></div></div></div></div>
<div><br></div><div><br></div>
=20
</div><div id=3D"ydpa95fb774yahoo_quoted_4954443257" class=3D"ydpa9=
5fb774yahoo_quoted">
<div style=3D"font-family:'Helvetica Neue', Helvetica, Arial, s=
ans-serif;font-size:13px;color:#26282a;">
=20
<div>
On Tuesday, October 12, 2021, 12:25:30 p.m. GMT-4, Sara=
h Finn <[email protected]> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id=3D"ydpa95fb774yiv6554140558"><div dir=3D"ltr">=
Great stuff Petr! </div><br><div class=3D"ydpa95fb774yiv6554140558gmai=
l_quote"><div dir=3D"ltr" class=3D"ydpa95fb774yiv6554140558gmail_attr">On T=
hu, 7 Oct 2021 at 21:26, Petr Bokoc <<a href=3D"mailto:[email protected]=
" target=3D"_blank" rel=3D"noreferrer noopener">[email protected]</a>> w=
rote:<br></div><blockquote class=3D"ydpa95fb774yiv6554140558gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex;"><div dir=3D"ltr">Hi everyone,<br>
<br>
Fedora 35 Beta is out now[0], so it's time to start writing release notes o=
nce again!<br>
<br>
As usual, we aim to cover notable Changes[1]. Ben Cotton has been=20
tracking those in our release-notes issues for us, which allows us to=20
grab a list of everything that needs to be documented[2]. Branch *f35*=20
is ready for your pull requests.<br>
<br>
=3D What to do<br>
<br>
1. Pick one or more issues in the list linked above.<br>
<br>
2. Open each issue you picked, and click the Take button on the right to
claim it. (If you claim an issue but later find out you don't have time
to write about it, remove yourself from the issue ASAP so others can=20
see it's free and take it!)<br>
<br>
3. Find some information about the issue. A lot of them have plenty of=20
info in them already; if not, find out who's responsible for the change,
and talk to them on IRC or via mail. Of course it's always better if=20
you try to do research before you ask questions. Note that you might not
always be able to reach the owner in a reasonable timeframe; in that=20
case just do your best, I'll be reviewing PRs, so if we publish=20
something wrong, it's on me.<br>
<br>
4. Write a release note about the issue. If you're not sure how exactly a
release note looks, check out some of the previous releases for=20
inspiration. We don't want any long, overly technical texts, the release
notes are generally meant to highlight changes, not to tell people how=20
to use something.<br>
<br>
5. Now the workflow diverges based on your permissions and technical skills=
: <br>
<br>
5a. If you know how to use git and asciidoc, we'd apprec=
iate it if you=20
wrote up the release note and sent a pull request against the main repo,
branch "f35". Your contributions should go into one of the files in=20
"modules/release-notes/pages/", which one exactly depends on the=20
contents of the change you're documenting. Use the "build.sh" and=20
"preview.sh" scripts in the repository root to preview your changes=20
locally; see the repository README for specific instructions. If you=20
can't see the section where you added your contributions at all, make=20
sure it's included in "modules/release-notes/nav.adoc".<br>
<br>
5b. If the above sounds like gibberish to you, it's fine=
: just add a
comment with your text into the issue, and ping me on IRC/Telegram/Matrix =
or=20
through e-mail[3]; I'll mark it up for you and make sure your=20
contribution appears in the final document.<br>
<br>
See also our contributor docs[4] for some additional info and tips;=20
especially the "Git for docs writers" section if you're not familiar=20
with the system.<br>
<br>
If anyone has any questions, go ahead and ask either here on the list or
on IRC, I'm happy to help. The current schedule shows the preferred=20
final release target on *October 19*, which gives us about 2 weeks to work =
with, which really isn't much. The release date may slip, but don't count o=
n it.<br>
<br>
Happy writing!<br>
<br>
Petr<br>
<br>
[0] <a href=3D"https://fedoramagazine.org/announcing-fedora-35-beta/" targe=
t=3D"_blank" rel=3D"noreferrer noopener">https://fedoramagazine.org/announc=
ing-fedora-35-beta/</a><br>
[1] <a href=3D"https://fedoraproject.org/wiki/Releases/35/ChangeSet" target=
=3D"_blank" rel=3D"noreferrer noopener">https://fedoraproject.org/wiki/Rele=
ases/35/ChangeSet</a><br>
[2] <a href=3D"https://pagure.io/fedora-docs/release-notes/issues?status=3D=
Open&search_pattern=3DF35&close_status=3D" target=3D"_blank" rel=3D=
"noreferrer noopener">https://pagure.io/fedora-docs/release-notes/issues?st=
atus=3DOpen&search_pattern=3DF35&close_status=3D</a><br>
[3] <a href=3D"https://docs.fedoraproject.org/en-US/fedora-docs/#find-docs"=
target=3D"_blank" rel=3D"noreferrer noopener">https://docs.fedoraproject.o=
rg/en-US/fedora-docs/#find-docs</a> <br>[4] <a href=3D"https://docs.fedorap=
roject.org/en-US/fedora-docs/" target=3D"_blank" rel=3D"noreferrer noopener=
">https://docs.fedoraproject.org/en-US/fedora-docs/</a></div>
_______________________________________________<br>
docs mailing list -- <a href=3D"mailto:[email protected]" target=
=3D"_blank" rel=3D"noreferrer noopener">[email protected]</a><br=
>
To unsubscribe send an email to <a href=3D"mailto:[email protected]=
oject.org" target=3D"_blank" rel=3D"noreferrer noopener">[email protected]=
edoraproject.org</a><br>
Fedora Code of Conduct: <a href=3D"https://docs.fedoraproject.org/en-US/pro=
ject/code-of-conduct/" target=3D"_blank" rel=3D"noreferrer noopener">https:=
//docs.fedoraproject.org/en-US/project/code-of-conduct/</a><br>
List Guidelines: <a href=3D"https://fedoraproject.org/wiki/Mailing_list_gui=
delines" target=3D"_blank" rel=3D"noreferrer noopener">https://fedoraprojec=
t.org/wiki/Mailing_list_guidelines</a><br>
List Archives: <a href=3D"https://lists.fedoraproject.org/archives/list/doc=
[email protected]" target=3D"_blank" rel=3D"noreferrer noopener">ht=
tps://lists.fedoraproject.org/archives/list/[email protected]</a=
><br>
Do not reply to spam on the list, report it: <a href=3D"https://pagure.io/f=
edora-infrastructure" target=3D"_blank" rel=3D"noreferrer noopener">https:/=
/pagure.io/fedora-infrastructure</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
class=3D"ydpa95fb774yiv6554140558gmail_signature"><div dir=3D"ltr"><div di=
r=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><p style=3D"color:rgb(0,0,0);fo=
nt-family:RedHatText, sans-serif;font-weight:bold;margin:0px;padding:0px;fo=
nt-size:14px;"><span>Sarah</span> <span>Finn</span><span style=3D"text=
-transform:uppercase;color:rgb(170,170,170);margin:0px;"></span></p><p styl=
e=3D"color:rgb(0,0,0);font-family:RedHatText, sans-serif;font-size:12px;mar=
gin:0px 0px 4px;text-transform:capitalize;">She/Her</p><p style=3D"color:rg=
b(0,0,0);font-family:RedHatText, sans-serif;font-size:12px;margin:0px;"><sp=
an>Senior Agile Practitioner</span></p><p style=3D"color:rgb(0,0,0);font-fa=
mily:RedHatText, sans-serif;font-size:12px;margin:0px;">Agile DevOps CoP Ma=
nager<span><br></span></p><p style=3D"color:rgb(0,0,0);font-family:RedHatTe=
xt, sans-serif;margin:0px 0px 4px;font-size:12px;"><a href=3D"https://www.r=
edhat.com/" style=3D"color:rgb(0,136,206);margin:0px;" target=3D"_blank" re=
l=3D"noreferrer noopener">Red Hat</a></p><div style=3D"color:rgb(0,0,0);fon=
t-family:RedHatText, sans-serif;font-size:medium;margin-bottom:4px;"><span>=
<p style=3D"font-size:12px;margin:0px;">Waterford, Ireland</p></span></div>=
<p style=3D"color:rgb(0,0,0);font-family:RedHatText, sans-serif;margin:0px;=
font-size:12px;"><span style=3D"margin:0px;padding:0px;"><a href=3D"mailto:=
[email protected]" style=3D"color:rgb(0,0,0);margin:0px;" target=3D"_blank" =
rel=3D"noreferrer noopener">[email protected]</a> </span><span><=
br>M: <a style=3D"color:rgb(0,0,0);margin:0px;" target=3D"_blank" rel=
=3D"noreferrer noopener">0879830832</a> </span></p><div s=
tyle=3D"color:rgb(0,0,0);font-family:RedHatText, sans-serif;font-size:12px;=
margin-bottom:8px;"><div><a href=3D"https://twitter.com/redhat" title=3D"tw=
itter" style=3D"background-color: transparent; background-repeat: no-repeat=
; background-attachment: scroll; background-image: url(https://static.redha=
t.com/libs/redhat/brand-assets/2/social/social-media--twitter--53x53.png); =
background-size: auto; color: rgb(0, 0, 0); display: inline-block; line-hei=
ght: 20px; padding-left: 14px;" target=3D"_blank" rel=3D"noreferrer noopene=
r"><span style=3D"margin-left:2px;">@RedHat</span></a> <a =
href=3D"https://www.linkedin.com/company/red-hat" title=3D"LinkedIn" style=
=3D"background-color: transparent; background-repeat: no-repeat; background=
-attachment: scroll; background-image: url(https://static.redhat.com/libs/r=
edhat/brand-assets/2/social/social-media--linkedin--53x46.png); background-=
size: auto; color: rgb(0, 0, 0); display: inline-block; line-height: 20px; =
padding-left: 14px; margin: 0px 4px 0px 3px; padding-top: 1px;" target=3D"_=
blank" rel=3D"noreferrer noopener"><span style=3D"margin-left:4px;">Red Hat=
</span></a> <a href=3D"https://www.facebook.com/RedHatInc" title=
=3D"Facebook" style=3D"background-color: transparent; background-repeat: no=
-repeat; background-attachment: scroll; background-image: url(https://stati=
c.redhat.com/libs/redhat/brand-assets/2/social/social-media--facebook--53x1=
3.png); background-size: auto; color: rgb(0, 0, 0); display: inline-block; =
line-height: 20px; padding-left: 12px; padding-top: 1px;" target=3D"_blank"=
rel=3D"noreferrer noopener"><span>Red Hat</span></a></div></div><div style=
=3D"margin-top:12px;"><table style=3D"color:rgb(0,0,0);font-family:RedHatTe=
xt, sans-serif;font-size:medium;" class=3D"yahoo-compose-table-card" border=
=3D"0"><tbody><tr><td width=3D"100px"><a href=3D"https://www.redhat.com/" t=
arget=3D"_blank" rel=3D"noreferrer noopener"><img src=3D"https://static.red=
hat.com/libs/redhat/brand-assets/2/corp/logo--200.png" data-inlineimagemani=
pulating=3D"true" width=3D"90" height=3D"auto"></a></td></tr></tbody></tabl=
e><div><table style=3D"color:rgb(34,34,34);font-family:Arial, Helvetica, sa=
ns-serif;font-size:small;" class=3D"yahoo-compose-table-card" border=3D"0">=
<tbody><tr><td width=3D"100px"><i><br></i></td></tr></tbody></table><i><fon=
t color=3D"#222222">"If you are not willing to risk the usual, you wil=
l have to settle for the ordinary."</font></i></div></div></div></div></div=
></div></div>
</div>_______________________________________________<br>docs mailing list =
-- <a href=3D"mailto:[email protected]" target=3D"_blank" rel=3D=
"noreferrer noopener">[email protected]</a><br>To unsubscribe se=
nd an email to <a href=3D"mailto:[email protected]" target=
=3D"_blank" rel=3D"noreferrer noopener">[email protected]<=
/a><br>Fedora Code of Conduct: <a href=3D"https://docs.fedoraproject.org/en=
-US/project/code-of-conduct/" target=3D"_blank" rel=3D"noreferrer noopener"=
>https://docs.fedoraproject.org/en-US/project/code-of-conduct/</a><br>List =
Guidelines: <a href=3D"https://fedoraproject.org/wiki/Mailing_list_guidelin=
es" target=3D"_blank" rel=3D"noreferrer noopener">https://fedoraproject.org=
/wiki/Mailing_list_guidelines</a><br>List Archives: <a href=3D"https://list=
s.fedoraproject.org/archives/list/[email protected]" target=3D"_=
blank" rel=3D"noreferrer noopener">https://lists.fedoraproject.org/archives=
/list/[email protected]</a><br>Do not reply to spam on the list,=
report it: <a href=3D"https://pagure.io/fedora-infrastructure" target=3D"_=
blank" rel=3D"noreferrer noopener">https://pagure.io/fedora-infrastructure<=
/a><br></div>
</div>
</div></body></html>
------=_Part_2344802_1111444170.1634072249127--
--===============2903380277871706374==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZG9jcyBtYWls
aW5nIGxpc3QgLS0gZG9jc0BsaXN0cy5mZWRvcmFwcm9qZWN0Lm9yZwpUbyB1bnN1YnNjcmliZSBz
ZW5kIGFuIGVtYWlsIHRvIGRvY3MtbGVhdmVAbGlzdHMuZmVkb3JhcHJvamVjdC5vcmcKRmVkb3Jh
IENvZGUgb2YgQ29uZHVjdDogaHR0cHM6Ly9kb2NzLmZlZG9yYXByb2plY3Qub3JnL2VuLVVTL3By
b2plY3QvY29kZS1vZi1jb25kdWN0LwpMaXN0IEd1aWRlbGluZXM6IGh0dHBzOi8vZmVkb3JhcHJv
amVjdC5vcmcvd2lraS9NYWlsaW5nX2xpc3RfZ3VpZGVsaW5lcwpMaXN0IEFyY2hpdmVzOiBodHRw
czovL2xpc3RzLmZlZG9yYXByb2plY3Qub3JnL2FyY2hpdmVzL2xpc3QvZG9jc0BsaXN0cy5mZWRv
cmFwcm9qZWN0Lm9yZwpEbyBub3QgcmVwbHkgdG8gc3BhbSBvbiB0aGUgbGlzdCwgcmVwb3J0IGl0
OiBodHRwczovL3BhZ3VyZS5pby9mZWRvcmEtaW5mcmFzdHJ1Y3R1cmUK
--===============2903380277871706374==--